Composio
Composio: A managed tool layer that generates per-user MCP URLs for toolkits such as Gmail, handles the app OAuth, and limits each server to an allowed list of tool slugs. Remote transport: HTTP. Price read 4 November 2026: Hobby 0 USD (100K tool calls a month), Pro 29 USD a month plus overage (0.
Fact sheet
| Product | Composio |
|---|
| Operator | Composio |
|---|
| Kind | tool gateway and host |
|---|
| Home | composio.dev |
|---|
| Pricing | Hobby 0 USD (100K tool calls a month), Pro 29 USD a month plus overage (0.0003 USD per tool call), Enterprise custom; read 2026-11-04. (source, read 4 November 2026) |
|---|
| In this directory | Composio: no MCP endpoint on record |
|---|
| Vendor profile | Composio |
|---|
Rubric
Composio on the host and registry rubric| Dimension | Value | Evidence | Source |
|---|
| Remote transport | HTTP | Server URL plus headers; transport variant not named. | docs.composio.dev, read 2026-11-04 |
| OAuth with client registration | Composio holds app OAuth | Users authenticate toolkits through auth configs; DCR not documented. | docs.composio.dev, read 2026-11-04 |
| Per-tool auth scoping | yes, allowed_tools | Tool slugs allowlisted per server. | docs.composio.dev, read 2026-11-04 |
| Hosting and scale limits | 2,000 to 10,000 requests a minute | Hobby 2,000 and Pro 10,000 requests per minute. | composio.dev, read 2026-11-04 |
| Observability | not detailed on these pages | No log feature described in the quickstart. | docs.composio.dev, read 2026-11-04 |
| Pricing | 0 / 29 USD / custom | Dated 2026-11-04. | composio.dev, read 2026-11-04 |
| Registry submission | not a registry | Composio generates servers; it does not list third parties. | docs.composio.dev, read 2026-11-04 |
| Discoverability by agents | session-based tool discovery | The page recommends sessions for dynamic tool access. | docs.composio.dev, read 2026-11-04 |
| Own server in the registries | yes | io.github.ComposioHQ/composio active in the official registry. | registry.modelcontextprotocol.io, read 2026-11-04 |
What it does not do
- Does not host your own MCP server code.
- Does not let you build the server URL from a server ID; you must generate it.
Dated facts
- Composio generates a user-specific MCP URL with composio.mcp.generate or POST /api/v3.1/mcp/servers/generate; consumer connections use https://connect.composio.dev/mcp. (docs.composio.dev, read 4 November 2026)
- Requests carry an x-api-key header, required by default for new organisations through require_mcp_api_key. (docs.composio.dev, read 4 November 2026)
- The allowed_tools parameter restricts a server to listed tool slugs such as GMAIL_FETCH_EMAILS. (docs.composio.dev, read 4 November 2026)
- Hobby is free with 100K tool calls a month (up to 20K on Composio-managed apps); Pro is 29 USD a month with tool-call overage at 0.0003 USD per call. (composio.dev, read 4 November 2026)
- New pricing applies to sign-ups from 15 Aug 2026; existing customers keep their plan through 31 Dec 2026. (composio.dev, dated 15 August 2026, read 4 November 2026)
- The quickstart uses both managed_auth_via_composio and managed_auth_by_composio in its examples, an inconsistency worth checking against the API reference. (docs.composio.dev, read 4 November 2026)
- Composio publishes io.github.ComposioHQ/composio in the official registry with remote https://connect.composio.dev/mcp. (registry.modelcontextprotocol.io, read 4 November 2026)
Compare and alternatives