The MCP tool directory.

Get detailed information about a specific MCP tool, scoped to one product. Pass both the productSlug and the tool name — same-named tools across products are distinct. Response: { tool: { normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt, position (always 1), rank (always 1.0) } }. Errors: { error: { code: 'not_found', ... } }.

Retrieve detailed information about a specific tool using its slug identifier. This endpoint returns full metadata about a tool including input/output parameters, versions, and toolkit information.

Retrieve a paginated list of available tools with comprehensive filtering, sorting and search capabilities. Use query parameters to narrow down results by toolkit, tags, or search terms.

List every (product, tool) pair that shares a normalized name. A disambiguation lookup — same name across providers does NOT mean the tools are interchangeable. Ranking basis: productName. Paid tier is NOT a ranking input — it appears only as an annotation. Every result carries { position (1-based), rank (0..1) } plus preflight annotations { accessModel, healthScore, readOnly, destructive }. Response: { normalizedName, total, tools[] (each: position, rank, productSlug, productName, displayName, description, inputSchema, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt) }.

Search for MCP tools by capability. Each result is one (product, tool) pair — tools sharing a name across providers are NOT interchangeable, so each provider's tool is its own row with its own description and input schema. Ranking basis: semantic relevance to the query (embedding search); on the lexical fallback (searchMode='lexical') results are name-ordered and rank does NOT reflect relevance. Paid tier is NOT a ranking input — it appears only as an annotation. Every result carries { position (1-based), rank (0..1; 1.0 = top) } so callers can merge results across tools consistently, plus preflight annotations { accessModel (open|keyed|account|commercial; whether an agent can call it without becoming a customer first), healthScore (0-100, nullable), readOnly, destructive } so you can judge callability and safety BEFORE selecting. Optional access filter narrows to a single access class. Response: { searchMode ('semantic'|'lexical'), tools: [{ position, rank, normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified (true when no approved vendor claim), verifiedAt (ISO; nullable) }] }. Errors: { error: { code: 'bad_input', ... } }.

Get detailed information about a specific analysis tool — use cases, assumptions, data requirements.

Execute an analysis tool. Returns a shareable interactive HTML report URL.

Get JSON schema for a tool — column_mapping and module_parameters required before tools_run.

Triage an issue by capturing a focused triage rationale and optionally applying metadata (labels, issue type, and issue fields) in a single operation. Use this tool when: - You are triaging a newly opened or untriaged issue for maintainers - You need to categorize the issue (type) and suggest/apply relevant labels - You want to record a brief, structured triage report Do not use this tool when: - The user is asking a general product question unrelated to triaging a specific issue triage_rationale should be concise markdown aimed at maintainers (not the issue author); it should contain: - Summary of the issue - Analysis of the problem or request - Suggested next steps or actions.

Retrieves all active trigger instances for your project. Triggers listen for events from connected accounts (e.g., new emails, Slack messages, GitHub commits) and can invoke webhooks or workflows. Use filters to find triggers for specific users, connected accounts, or trigger types.

Permanently deletes a trigger instance. This stops the trigger from listening for events and removes it from your project. Use the PATCH endpoint with status "disable" if you want to temporarily pause a trigger instead.

Updates the status of a trigger instance to enable or disable it. Disabling a trigger pauses event listening without deleting the trigger configuration. Re-enabling restores the trigger to its active state. Use this for temporary maintenance or to control trigger execution.

Creates a new trigger instance or updates an existing one with the same configuration. Triggers listen for events from external services (webhooks or polling) and can invoke your workflows. If a matching trigger already exists and is disabled, it will be re-enabled. Requires a connected account ID to associate the trigger with a specific user connection.

Retrieve detailed information about a specific trigger type using its slug identifier

Retrieve a list of available trigger types with optional filtering by toolkit. Results are paginated and can be filtered by toolkit.

Retrieves a list of all available trigger type enum values that can be used across the API from latest versions of the toolkit only

Search international treaties (조약 목록 조회). This tool searches Korean international treaties concluded and in effect with foreign countries and international organizations. Args: query: Search keyword (default "*") display: Number of results per page (max 100, default 20) page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" search: Search type (1=조약명, 2=본문검색) sort: Sort order - "lasc"|"ldes"|"dasc"|"ddes"|"nasc"|"ndes" gana: Dictionary search (ga, na, da, ...) eft_yd: Effective date range (YYYYMMDD~YYYYMMDD) conc_yd: Conclusion date range (YYYYMMDD~YYYYMMDD) cls: Treaty type - 1=양자 (bilateral), 2=다자 (multilateral) nat_cd: Country code filter ctx: MCP context (injected automatically) Returns: Search results with treaty list or error Examples: Search bilateral treaties with the US: >>> trty_search(query="미합중국", cls=1) Search multilateral treaties: >>> trty_search(cls=2, display=20)

Retrieve treaty full text (조약 본문 조회). This tool retrieves the complete text of a Korean international treaty. Args: id: Treaty sequence number (조약일련번호, required) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" ctx: MCP context (injected automatically) Returns: Full treaty text with details or error Examples: Retrieve a treaty by ID: >>> trty_service(id="123")

Update notes for a CRM conversation in a product scope.

Update an existing pull request in a GitHub repository.

Update the branch of a pull request with the latest changes from the base branch.

Replace entire content of an existing soul. Admin-only operation.

Update a contact record in Clay. This endpoint should only be used when you need to update a contact, not for adding contacts to groups.

Update a group or list. Use this to update the group title and/or modify its members. When adding or removing contacts, provide ALL contact IDs to add/remove in a single call - do not make multiple calls for individual contacts.

Updates page property values for the specified page.

Create/update a conversation note for a product scope conversation.

Fetches and extracts content from a given webpage URL. Input the URL of the webpage you want to extract content from as a string using the url parameter. You can also input an array of URLs to fetch content from multiple pages at once.

Get the details of an existing email verification code that can be used to send an email to a user for verification.

Accepts an invitation and, if linked to an organization, activates the user's membership in that organization.

Retrieve an existing invitation using the token.