← Back to all projects

composio

Hosted catalogue of ready-made actions across 1000+ apps, with the sign-in handled

OfficialMIT
Stars
30.8k
Forks
4.9k
Open issues
126
Last commit
30 Oct 2026

What is composio?

Composio hands an agent a catalogue of ready-made actions spread across more than a thousand apps — create a GitHub issue, fetch Gmail threads — and keeps each of your users' account connections stored and refreshed, so you never write a sign-in flow yourself. A session is scoped to one user and by default gives the model only a handful of meta tools for finding, authenticating and running things at runtime, so hundreds of tool definitions never fill the context window; app events arrive as signed webhooks, and the agent gets a persistent Python sandbox to work in. The trade-off is that none of that machinery is yours: you gain a thousand integrations you did not have to build, and give up the ability to change any of them.

What can you do with composio?

  • App actions already written, and named after what they do — Tools are named for the app and the action — GITHUB_CREATE_ISSUE, GMAIL_FETCH_EMAILS — and each carries an input schema for its parameters and an output schema for what comes back. Composio's docs list 1,181 toolkits; Gmail alone holds more than fifty tools.
  • Sign-in is one link, and the token stays with Composio — When a task needs an account, the session issues a connect link and the user follows it to the app's own sign-in — Google's, GitHub's, Slack's. Composio stores and refreshes the resulting connection against your user id, and its docs note that credentials never pass through your app or the model.
  • The agent searches for tools instead of loading them all — By default a session hands the model only meta tools that discover, authenticate and execute at runtime, so the catalogue never enters the context window. Store the session id and reopen it on the next turn; a DIRECT_TOOLS preset loads chosen tools up front instead.
  • Fence a session in before you trust it — You can enable or disable whole toolkits, list the individual tools inside one, and filter on behaviour hints such as read-only or destructive. Worth doing early: with no toolkits set, the agent can find anything in the catalogue at runtime.
  • App events arrive as signed webhooks — You register one webhook URL per project and Composio posts every trigger event there, signed so you can verify it. Some events a provider pushes the moment they happen; others Composio polls for, and it puts those up to about fifteen minutes behind on its own managed auth.
  • Reach it over MCP, or straight from a shell — A session can expose a hosted MCP endpoint that Claude, Cursor or any MCP client connects to with no adapter package — though Composio's docs warn that before- and after-execution hooks and tools defined in your own process do not run over that route. The composio CLI covers search, execute and account linking from the terminal.

Before you choose composio

  • This repository is the client side only — SDKs, adapters and CLI — while the toolkits, the stored logins and the sandbox run on Composio's servers behind an API key, and your own cloud is an Enterprise arrangement.
  • Usage is metered: as listed in August 2026 the free tier covers 100,000 tool calls and 50,000 trigger events a month, after which the $29 Pro plan charges $0.0003 per tool call and $0.003 per trigger event.
  • Connectors are Composio's to fix rather than yours: as of August 2026 the tracker still carried unresolved per-app defects in Google Drive folder creation, the Basecamp toolkit and YouTube video upload.Reported in#3860#3809

Star history

17 Aug to 30 Oct · +1.1k

29.7k30.8k

Frequently asked questions

Is composio free for commercial use?

composio is released under the MIT licence — OSI-approved open source, which permits commercial use.

How can composio be deployed?

composio is available as Managed cloud.