Composio MCP Server

About

Composio exposes its toolkit platform — 1,000+ toolkits with managed authentication, tool search, context management and a sandboxed workbench — over MCP, which makes it a hosted multi-tool endpoint rather than a single-purpose server you run locally. A correction worth stating plainly, because this catalog carried the wrong link: the project is `ComposioHQ/composio` (29,000+ stars, actively pushed), not `ComposioHQ/composio-mcp-plugin`, which is a small three-star side repo for MCP registry plugins. The working model is create-then-generate. You define a server config against one or more toolkits — in Python, `composio.mcp.create(name="my-gmail-server", toolkits=[{"toolkit": "gmail", "auth_config": "ac_xyz123"}], allowed_tools=["GMAIL_FETCH_EMAILS", "GMAIL_SEND_EMAIL"])` — and then mint a per-user URL from it with `composio.mcp.generate(user_id="user-123", mcp_config_id=server.id)`. The URL that comes back has the shape `https://backend.composio.dev/v3/mcp/<SERVER_ID>?user_id=<USER_ID>`, and connections must send an `x-api-key` header carrying your Composio API key — that is required whenever `require_mcp_api_key` is enabled, which is the default for newly created organisations. Two prerequisites trip people up: an auth config for the toolkit has to exist before `create()` will accept it, and the end user has to have authenticated with that toolkit before their generated URL returns anything useful, because handling that OAuth is the point of the platform. Server management is symmetrical and scriptable — `composio.mcp.list()` (filterable by toolkit, with a `limit`), `.get()`, `.update()` to rename or narrow `allowed_tools`, and `.delete()` — and the same configs are editable from the Composio dashboard. SDKs install with `uv add composio` for Python or `@composio/core` for TypeScript, and `@composio/mcp` (v1.0.9 on npm) is a separate small MCP CLI that exposes an `mcp` binary for wiring clients like Claude, Cursor and Windsurf from the command line. Because the endpoint is a plain remote MCP URL with headers, it drops straight into provider-native MCP support — the OpenAI Responses API, for example, takes it as a `{"type": "mcp", "server_url": …, "headers": {"x-api-key": …}}` tool. One caveat from Composio's own documentation: single-toolkit MCP servers are the older path, and for most use cases they now steer you to sessions instead, which give dynamic tool access and let Composio handle context management rather than pinning a fixed tool list per server.

Installation

npx @composio/mcp@latest

Categories

Works With

Frequently Asked Questions