Dynamic tool discovery
Sessions can search and load tools from the Composio catalog with context management.
Documentation ↗MCP server / integration platform / source-linked
Composio MCP
Composio MCP is a hosted integration layer that creates per-user sessions and exposes selected SaaS toolkits through a portable MCP URL. The current docs recommend sessions over a static single-toolkit server because sessions provide dynamic tool access and context management. Toolkits, auth configs, allowed tools, and project-scoped API keys can be combined into a controlled session.
Before you choose.
Identify the implementation and the job it supports.
Composio MCP is a hosted integration layer that creates per-user sessions and exposes selected SaaS toolkits through a portable MCP URL. The current docs recommend sessions over a static single-toolkit server because sessions provide dynamic tool access and context management. Toolkits, auth configs, allowed tools, and project-scoped API keys can be combined into a controlled session.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Hosted Streamable HTTP
- Authentication
- Composio project or user API key carried in x-api-key/x-user-api-key headers; underlying toolkit auth configs handle OAuth connections.
Create a session for a user, attach toolkits/auth configs or a saved session policy, set mcp=true, and pass session.mcp.url plus headers to the MCP client.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
session = composio.sessions.create(user_id="user_123", toolkits=["gmail"], mcp=True)
url = session.mcp.urlWhat it actually exposes.
Concrete capabilities with maintainer sources.
Hosted per-user MCP
Expose a session-specific MCP endpoint that uses the same toolkits, auth configs, and connected accounts as the SDK session.
Documentation ↗Tool policy controls
Enable toolkits/tools or a direct-tools preset to expose exactly the operations a client should see.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
Signal: centralized onboarding
The user sees value in one MCP endpoint and managed connections for multiple services, especially for onboarding colleagues who would struggle with editing client JSON files.
“log into all your services there and just set one MCP up for all of them”Open community source ↗
Signal: oauth reconnect reliability
A Hermes Agent issue reports an OAuth async-generator cleanup problem that poisoned a lock; repeated reconnects then parked the Composio endpoint for hours without reaching the network.
“MCP server 'composio' keepalive failed, triggering reconnect”Open community source ↗
Signal: support and cost risk
A founder comment says early integration support later disappeared and recurring charges became unexpectedly high, making exit difficult; this is an unverified individual account.
“I’m being charged hundreds of dollars every month.”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Scoped SaaS research session
Suggested evaluation, not an observed test result.
- Create a project-key session with one toolkit and only read/search tools enabled.
- Give the session URL and returned headers to the MCP client.
- Review tool output and expand the policy only when the workflow needs another action.
What to inspect: A portable but policy-bounded SaaS session with explicit user/account context. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
MCP calls bypass SDK beforeExecute/afterExecute hooks and schema modifiers, so SDK-side interception does not apply to direct MCP calls.
Boundary reference ↗User-only API-key sessions can reach every project the user can access; project-key sessions are safer for narrow deployments.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A portable but policy-bounded SaaS session with explicit user/account context. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Zapier MCP | Choose for a simpler one-endpoint app-action catalog with OAuth or connection tokens. | Zapier is simpler to connect but uses task-based billing and one server per client. Documentation ↗ |
| Pipedream MCP | Choose when your product needs per-end-user app connections and custom tools. | Pipedream requires project/environment/external-user headers and more integration plumbing. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Why use sessions?
Composio recommends sessions for dynamic tools and context management instead of a static single-toolkit server.
Documentation ↗
Are returned headers secret?
Yes. Treat session.mcp.headers as a credential and prefer a project key for narrow access.
Documentation ↗
Source trail.
Maintainer documentation used in this record.