The MCP tool directory.

Register the on-chain EscrowCreate transaction hash with the referee. Call this after submitting the EscrowCreate transaction on XRPL. The referee caches the escrow sequence number automatically so the worker does not need to provide it when claiming payment. Returns: status: "confirmed", sequence: escrow sequence number.

Create a new Connect Application. Supports both OAuth and Machine-to-Machine (M2M) application types.

Delete an existing Connect Application.

Retrieve details for a specific Connect Application by ID or client ID.

List all Connect Applications in the current environment with optional filtering.

Update an existing Connect Application. For OAuth applications, you can update redirect URIs. For all applications, you can update the name, description, and scopes.

List all connections in a namespace. Supports filtering by metadata using `metadata.{key}={value}` query params.

Create a new MCP connection with an auto-generated ID. Requires API key and namespace ownership.

Delete a connection and terminate its MCP session. Requires API key and namespace ownership.

Get details for a specific connection. Requires service token with connections:read scope.

Create a namespace-scoped subscription that receives events from every connection in the namespace.

Delete a namespace-scoped trigger subscription.

List namespace-scoped trigger subscriptions for all connections in the namespace.

Create a connection-scoped subscription that receives events from one connection.

Delete a connection-scoped trigger subscription.

List trigger subscriptions scoped to a single connection.

Get the schema for a single trigger type.

Create a trigger instance for a connection using the trigger's declared params.

Delete a trigger instance and deregister its upstream webhook.

Get a specific trigger instance for a connection.

List trigger types exposed by a connection.

Create or update an MCP connection with the given ID. mcpUrl is required when creating a new connection, but optional when updating. Returns 409 if a different mcpUrl is provided, except while the connection is input_required and the new URL keeps the same host and path.

Initiates a new connection to an external service for a user. For OAuth-based toolkits, this returns a redirect URL to complete authentication. For API key-based toolkits, provide the credentials directly in the request body. Use the `user_id` field to associate the connection with a specific user in your system. **Deprecated for Composio-managed OAuth:** For Composio-managed auth configs on OAuth1, OAuth2, or DCR_OAUTH schemes, this endpoint is being retired and will start returning `400 BadRequest` on **2026-05-08** for new organizations and **2026-07-03** for all remaining organizations. Migrate those calls to `POST /api/v3/connected_accounts/link`. Custom auth configs and non-OAuth schemes (API key, bearer, basic) continue to be supported here. Responses on the retiring path carry a `Deprecation` header (RFC 9745) and a `Sunset` header (RFC 8594) for client-side detection.

Soft-deletes a connected account by marking it as deleted in the database. This prevents the account from being used for API calls but preserves the record for audit purposes.

Retrieves comprehensive details of a connected account, including authentication configuration, connection status, and all parameters needed for API requests.

Creates a new authentication link session that users can use to connect their accounts

Retrieves all connected accounts for your project. Connected accounts represent authenticated user connections to external services (e.g., a user's Gmail account, Slack workspace). Filter by toolkit, status, user ID, or auth config to find specific connections.

Initiates a new authentication flow for a connected account when credentials have expired or become invalid. This may generate a new authentication URL for OAuth flows or refresh tokens for other auth schemes.

Updates the status of a connected account to either enabled (active) or disabled (inactive). Disabled accounts cannot be used for API calls but remain in the database.

Update a connected account. Supports updating the alias and/or credentials. Only specified fields will be updated. Set a credential field to null to remove it. Alias must be unique within the same project, entity, and toolkit scope.