Hosted tool-calling platform with 1,500+ app connectors, managed OAuth and a per-session MCP endpoint; free to 100,000 tool calls a month.
Teams building agents that need to act inside a lot of third-party SaaS accounts without writing an OAuth flow per app, since Composio states that managed auth covers OAuth, API keys and token refresh end to end and is the default. It suits per-user products: the README describes per-user sessions that can be restricted to specific toolkits, auth configs and connected accounts, and every session can expose a hosted MCP endpoint by passing mcp: true. The $0 Hobby plan at 100,000 tool calls a month with no credit card makes it a realistic place to prototype before committing.
Anyone who needs to run the gateway inside their own infrastructure should look elsewhere: the MIT licence covers the SDKs (@composio/core and composio), and neither the docs welcome page nor the GitHub README mentions self-hosting the platform or the MCP endpoint. Buyers who want one predictable line item will find the Pro plan hard to forecast, because on top of $29/mo and $0.0003 per tool call the pricing page meters white-labelling at $0.30 per connection, IP allowlist at +$0.0001 per call, BAA at +$0.0003 per call, zero data retention at +$0.0001 per call, and separate rates for shared connections, direct execution, proxy execute, sandbox execution and sandbox LLM tokens. Regulated teams needing SSO, SCIM or customer-managed keys cannot buy them at list price at all, as those are Enterprise-only.
Pros
Cons
There is a genuinely free Hobby plan at $0 with no credit card: 100,000 tool calls and 50,000 trigger events a month, 3 team members and unlimited connected accounts. It is hard-capped, so usage pauses at the limit until the next month or until you upgrade. One catch: Composio-managed OAuth apps only draw on 20K of those 100K calls unless you supply your own OAuth app.
Yes, and the site says managed auth is the default. Composio states it manages OAuth flows end to end along with API keys, token refresh and lifecycle, with granular scopes per connected account and encrypted tokens and keys. Connections need a one-time user sign-in per app. You can also bring your own OAuth app, which the pricing page says unlocks the full 100,000 free monthly tool calls.
Not based on anything the vendor publishes. The TypeScript and Python SDKs are MIT-licensed and open on GitHub, but the docs welcome page and the repo README both describe a hosted MCP endpoint and hosted sessions, and neither mentions self-hosting the platform. Treat Composio as a closed hosted service with open-source client libraries. If running the gateway in your own VPC is a hard requirement, confirm with Composio before building.
Composio exposes a hosted MCP endpoint per session, and the homepage says it works with any AI tool that can connect to an MCP server, with Cursor set up by pasting a single MCP URL. The docs name Claude Desktop and Cursor as example clients and mention native agent plugins for Claude Code and Codex. Framework adapters cover OpenAI Agents, Claude Agent SDK, LangChain, LangGraph and the Vercel AI SDK.
Facts sourced from the vendor’s own site, last verified 2026-10-10.
The Weekly Source
One email a week. New listings, repriced tools, and the ones we would skip - including this one if its pricing changes.
