Hosting

Composio-hosted remote MCP; upstream provider API accessed through a third-party toolkit

Transport

Streamable HTTP

Endpoint

https://connect.composio.dev/mcp

Authentication

API key. Composio Connect prompts the user to authorize or configure the provider connection; Composio-managed OAuth availability depends on the toolkit.

Requirements

• A Ashby account with permissions for the requested data and actions.
• A Composio account and MCP client supporting Streamable HTTP.
• Provider authorization or credentials as specified on the linked toolkit page.

Setup steps

1. Add https://connect.composio.dev/mcp as a remote Streamable HTTP MCP server.
2. When needed, ask the client to connect the Ashby app; complete the provider authorization in the browser or the secure credential flow.
3. Create or obtain the Ashby API key with the minimum required role and enter it only in Composio’s secure connection flow.
4. Use Composio tool search to discover available actions and fetch their schemas; the shared MCP exposes meta-tools rather than a fixed per-provider tools/list.
5. Start with a read-only query. Confirm before creating, sending, changing, or deleting provider data.

Composio toolkit reference documents 125 Ashby provider actions. Composio Connect discovers actions through shared meta-tools, so this is not a live per-connection tools/list.

• COMPOSIO_SEARCH_TOOLS

  Search the Composio action catalog for tools relevant to a request and return a suggested execution plan.

  01
• COMPOSIO_GET_TOOL_SCHEMAS

  Fetch input schemas for tool slugs returned by search.

  02
• COMPOSIO_MULTI_EXECUTE_TOOL

  Execute one or more discovered provider tools in parallel across connected apps.

  03
• COMPOSIO_MANAGE_CONNECTIONS

  Create, list, rename, or remove OAuth connections to upstream apps.

  04
• COMPOSIO_WAIT_FOR_CONNECTIONS

  Wait for a user to complete an OAuth connection flow.

  05
• COMPOSIO_REMOTE_WORKBENCH

  Run Python in a remote sandbox for bulk operations and processing large tool responses.

  06
• COMPOSIO_REMOTE_BASH_TOOL

  Run Bash in a remote sandbox for file processing and large data handling.

  07

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Third-party platform-mediated integration, not a standalone or vendor-hosted MCP server.
• Available actions depend on Composio toolkit version, provider permissions, account plan, and authorization.
• The toolkit contains write-capable recruiting actions; protect candidate personal data and confirm mutations.
• Connection and functionality were not tested in this research pass.

• third party mcp setup

  Composio documents the shared endpoint, Streamable HTTP transport, dynamic app authorization, and seven shared meta-tools.

• third party toolkit reference

  Composio toolkit reference lists 125 Ashby provider actions; Composio Connect uses shared meta-tools and dynamic discovery, so 125 is the documented toolkit action count, not a live tools/list count.

• official crawl4ai verification

  Crawl4AI 0.9.5 fetched Composio Connect docs and verified seven shared meta-tool identifiers. Provider toolkit actions are selected dynamically.

Documentation checked 2026-10-28T17:30:00.000Z. Connection has not been runtime tested.