What is Composio?
Composio gives an AI agent tools for more than 1,000 apps, such as Gmail, Slack, GitHub, Linear and HubSpot, and handles the OAuth sign-in and token storage for each of your users. You reach it three ways: Python and TypeScript SDKs that create a session per user, a CLI for coding agents, or a hosted MCP server. Composio Connect, at https://connect.composio.dev/mcp, is the shared endpoint for MCP clients and is listed in the official MCP Registry; every SDK session can also expose its own MCP URL.
Instead of loading hundreds of tool definitions, a session gives the agent seven meta-tools that search for the right tool, start an OAuth flow when an app is not yet connected, and execute calls. Sessions also include a sandbox, the Workbench, for processing files and large responses outside the model's context.
The SDK monorepo, ComposioHQ/composio, is MIT-licensed with about 30,800 GitHub stars, but the execution platform, credential vault and toolkits are a hosted service that needs a Composio API key. There is no self-hosted edition.
How to install Composio
https://connect.composio.dev/mcpIs Composio worth it?
Composio's real product is managed authentication at the level of your end users, not tools. Each session is tied to a user ID from your app, so when an agent needs that user's Gmail or Jira it gets their token, and the first time it needs an app Composio returns a sign-in link instead of failing. That is the part teams underestimate when they wire integrations themselves, and it is why Composio competes more with Pipedream Connect than with Zapier MCP.
The meta-tool design is the right call for context budgets. Rather than flooding the model with every action for every app, the agent searches, then loads what it needs. Provider packages adapt the tools for the OpenAI Agents SDK, the Claude Agent SDK, Vercel AI SDK, LangChain, LangGraph, LlamaIndex, Mastra, CrewAI and others, and the docs show the same session working over MCP.
The pricing, reset on 15 August 2026, is generous at the bottom. Hobby includes 100,000 tool calls and 50,000 trigger events a month and simply stops at the limit. Pro is $29 a month, which is a $29 usage credit that does not roll over, with calls at $0.0003 each and triggers at $0.003. Calls that use Composio's own shared OAuth apps cost more past 20,000 a month, at $0.0005, which is a nudge to register your own OAuth clients. API limits are 2,000 requests a minute on Hobby and 10,000 on Pro, per organisation.
Data handling deserves a decision before launch. By default Composio stores the arguments and responses of every tool call for up to one year. Zero Data Retention removes payloads from logs but is a paid add-on at $0.0001 per call on Pro, and the docs say it covers only some features. Composio says it is SOC 2 Type II and does not train on payloads, but it may train on de-identified execution metadata. With managed auth, provider quotas such as a Google Ads developer token can be shared across every connection that uses Composio's provider credentials until you bring your own app.
The SDK being MIT matters less than the star count suggests: everything runs through Composio's cloud, so the open-source part protects you from lock-in in your code, not in your credentials. Seen that way it is a fair trade, and the free tier is large enough to find out whether the hosted half earns its keep.
Where it earns its place
A four-engineer startup shipping an AI executive assistant
Let each customer connect Gmail, Google Calendar and Slack without building OAuth flows
Create a session per customer ID and pass session.tools() to the agent; unconnected apps return a sign-in link. On Pro, 300,000 calls a month comes to about $60 in total: the first 100,000 are free, the rest cost $0.0003 each, and the $29 fee is credited against that usage.
A developer using Claude Code across a dozen work apps
File Linear issues and read GitHub and Notion from the terminal
Install the CLI or add https://connect.composio.dev/mcp to the client and approve each app once in the browser. Personal volumes sit well inside Hobby's 100,000 free calls.
A compliance lead at a healthcare SaaS vendor
Approve an agent feature that touches patient-adjacent email
Budget for the BAA add-on at $0.0003 per call and ZDR at $0.0001 on Pro, or Enterprise where both are included; check which features ZDR does not cover before signing.
Before you commit
- Setup
- pip install composio or npm install @composio/core plus a provider package, a COMPOSIO_API_KEY, then composio.create(user_id) and session.tools(); MCP clients only need the Connect URL and a browser sign-in.
- Integrations
- 1,000+ toolkits per the README (the docs index now says 1,600+), triggers by webhook, Proxy Execute for raw API calls, and adapters for OpenAI, Anthropic, Claude Agent SDK, Vercel AI SDK, Google ADK, LangChain, LlamaIndex, Mastra, CrewAI and AutoGen.
- Data and privacy
- Credentials encrypted with AES-256-GCM and redacted from API responses; tool-call arguments and responses logged for up to one year by default; payloads not used for training, de-identified metadata may be; SOC 2 Type II.
- Cost at scale
- One million tool calls a month on Pro is about $270, since the first 100,000 are free and the $29 fee counts as credit; ZDR adds $100 and a BAA $300 at that volume; shared OAuth apps cost $0.0005 a call past 20,000.
- Limits
- 2,000 requests a minute on Hobby and 10,000 on Pro, shared across all endpoints; Hobby stops at its quota; provider quotas still apply and are shared under managed auth.
What's good
- Per-user OAuth and token refresh for 1,000+ apps
- Meta-tools keep tool definitions out of the context window
- 100,000 free tool calls a month; Pro calls at $0.0003
- SDK adapters for a dozen agent frameworks, plus MCP
What's not
- Tool payloads kept for up to a year unless you pay for ZDR
- No self-hosted edition; credentials live in Composio's cloud
- Shared OAuth apps share provider quotas and cost more past 20,000 calls
- SSO, SCIM and BAA are Enterprise or paid add-ons
Best for
Teams building agents that act in their customers' own SaaS accounts and do not want to run an OAuth vault.
Composio alternatives
Composio: common questions
- Is Composio worth it?
- The per-user OAuth plumbing every agent product ends up rebuilding, sold at a fraction of a cent per call, with a year of your tool payloads kept by default. We rate it 4.3 out of 5.
- How much does Composio cost?
- Hobby free with 100,000 tool calls and 50,000 triggers a month; Pro $29/month including $29 of usage credit, then $0.0003 per tool call; Enterprise custom. Applies to sign-ups from 15 August 2026.
- What are the downsides of Composio?
- Tool payloads kept for up to a year unless you pay for ZDR; no self-hosted edition; credentials live in Composio's cloud; shared OAuth apps share provider quotas and cost more past 20,000 calls; sSO, SCIM and BAA are Enterprise or paid add-ons.
- Who is Composio best for?
- Teams building agents that act in their customers' own SaaS accounts and do not want to run an OAuth vault.
- How much does Composio cost for a team or in production?
- One million tool calls a month on Pro is about $270, since the first 100,000 are free and the $29 fee counts as credit; ZDR adds $100 and a BAA $300 at that volume; shared OAuth apps cost $0.0005 a call past 20,000.
- Is Composio safe for company data?
- Credentials encrypted with AES-256-GCM and redacted from API responses; tool-call arguments and responses logged for up to one year by default; payloads not used for training, de-identified metadata may be; SOC 2 Type II.
- What are the best Composio alternatives?
- The closest alternatives we have reviewed are Pipedream MCP and Connect and Zapier MCP.
Answers checked Oct 26, 2026.
Make Composio? Show this rating on your site
