MCP server · Composio

composio-mcp.yml

Composio exposes its 1000+ toolkits over the Model Context Protocol as a hosted, per-session MCP server. The recommended path is the Tool Router: create a session with `mcp: true` and read the hosted endpoint off `session.mcp.url` with auth headers in `session.mcp.headers`. A single Tool Router MCP endpoint dynamically discovers, authenticates, and executes tools across all connected toolkits, so the tool surface is dynamic rather than a fixed manifest. The standalone MCP-server management API (create/list/delete named servers) still exists but Composio directs new integrations to session-based MCP.

Open docs → Composio provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Composio Type: Documentation link Transport: Host: docs.composio.dev

Documentation

https://docs.composio.dev/docs/sessions-via-mcp

Documentation link · transport

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.