cloudparts

Composio

A hosted tool layer for AI agents: one session per end user gives the model a few meta tools to search, authorize and run actions across more than 1,500 app toolkits, with Composio holding and refreshing the OAuth tokens.

What it is
Agent tools and integrations
Type
Commercial product
Made by
Sampark Inc.
License
Proprietary service; MIT-licensed SDKs
Facts checked
13 October 2026
Website Source code

What it is

Your code calls composio.create(user_id) and gets a session: the user, the toolkits in scope, their connected accounts and a remote sandbox. Instead of loading hundreds of tool definitions into the model’s context, the session hands the model a small fixed set of meta tools. The model searches for a tool such as GITHUB_CREATE_ISSUE, asks for a connection if the user has none, and runs it, and every call goes back through session.execute() to Composio’s servers, which call the app’s API as that user. Large responses can be written to the session’s sandbox, where the agent filters them with Python rather than pasting them into its context.

Authentication is the part Composio takes off your hands. When a tool needs an account, the COMPOSIO_MANAGE_CONNECTIONS meta tool returns a hosted Connect Link; the user signs in there, and Composio stores the token under your user_id and refreshes it. Credentials never pass through your app or the model. By default it uses Composio’s own shared OAuth apps; you bring your own app for your branding and scopes. The same session works through provider packages that reshape tools for OpenAI, Anthropic, LangChain and other frameworks, or as a hosted MCP endpoint (session.mcp.url) for any MCP client.

The company behind it is Sampark Inc., which does business as Composio. The Python and TypeScript SDKs are MIT-licensed on GitHub, but tool execution, token storage and the toolkit catalog run in Composio’s cloud. The Hobby plan is free with 100,000 tool calls a month; past the free amounts, tool calls cost $0.0003 each, meta tools such as tool search are free, and Pro is $29 a month with that much usage credit included.

Why teams pick it

  • OAuth handled end to end: hosted consent pages, token storage and refresh per user, so the model and your backend never see raw credentials
  • Context stays small: a handful of meta tools instead of every tool definition, and a sandbox for large results
  • One session, many front ends: provider packages for common agent frameworks, or the same session as a hosted MCP server
  • Cheap to start: 100,000 tool calls a month free, then $0.0003 per call, with spend caps on Pro

Watch out for

  • Every call runs through Composio’s cloud, so it holds your users’ tokens and sees tool traffic; zero data retention and a HIPAA BAA are paid add-ons on Pro
  • Rate limits are per organization across all endpoints: 2,000 requests a minute on Hobby and 10,000 on Pro
  • Composio’s shared OAuth apps are the easy default but count against lower allowances (20,000 of the free 100,000 tool calls) and cost an extra $0.0002 per call; scaling means registering your own OAuth apps
  • The API has moved fast: sessions replaced direct execution in 2026, REST v3.1 changed tool-version defaults, and older “entity”, “action” and “integration” tutorials no longer match the SDK

Alternatives

What all agent tools and integrations have in common →Compare side by side →
GlamaCommercialThe largest public directory of MCP servers, which builds and runs each open-source server in a Firecracker sandbox to record its tools, score their descriptions and flag risky behavior, plus hosting and a gateway for the servers you use.Model Context Protocol (MCP)Open sourceAn open protocol, built on JSON-RPC, that lets an AI application discover and call tools, read resources and use prompt templates from any server that speaks it, so one integration works across Claude, ChatGPT, Cursor, VS Code and other clients.OneRenamedCommercialA hosted connection layer for AI agents, formerly Pica: you connect each app once in your own account, and every agent reaches it through one MCP server or CLI, with per-action scopes enforced and logged on each call.OpenAPI SearchOpen sourceA small, open directory of OpenAPI descriptions for popular APIs, with an MCP server that turns any of them, or any spec URL, into a short plain-language summary an AI model can read before writing calls.SpeakeasyCommercialGenerates typed SDKs, Terraform providers, CLIs and MCP servers from an OpenAPI document, and now also sells a hosted MCP platform and an enterprise MCP gateway that governs which agents may call which tools.

How it fits with other technologies

Give one user’s agent tools through a session · python

from composio import Composio

composio = Composio()  # reads COMPOSIO_API_KEY; default provider formats tools for OpenAI

# A session scopes the user, their connected accounts and the toolkits in reach
session = composio.sessions.create(user_id="user_123", toolkits=["github", "gmail"])
tools = session.tools()  # a few meta tools, not hundreds of tool schemas

# Pass `tools` to the model; run every tool call it makes through the session
result = session.execute(
    "COMPOSIO_SEARCH_TOOLS",
    arguments={"queries": [{"use_case": "send an email"}]},
)

# Or expose the same kind of session to any MCP client
mcp_session = composio.sessions.create(user_id="user_123", mcp=True)
print(mcp_session.mcp.url)

See it in a real stack

No architecture uses Composio yet. Drop it into the playground and wire it up yourself.Open playground →
Where it came from2023–2026

Once language models could call functions, every agent team hit the same chores: write a wrapper for each API, run an OAuth flow for each user and app, store and refresh the tokens, and keep the wrappers working as the APIs changed. Composio, founded in 2023 by Soham Ganatra and Karan Vaidya, with offices in San Francisco and Bengaluru, set out to do that once for everyone, as a catalog of ready-made tools with the authentication handled in its cloud. Its open-source SDK repository on GitHub dates from February 2024.

In mid-2025 Composio rebuilt its platform and released new v3 SDKs, renaming its concepts along the way because, its engineers wrote, users kept asking what an “integration”, a “connection” and an “app” each meant: actions became tools, apps became toolkits, integrations became auth configs and entity IDs became user IDs. In July 2025 Ganatra announced $29 million in total funding, including a $25 million Series A led by Lightspeed Venture Partners, to build “skills that evolve with your agents”, so that what one agent learns about a tool helps every other agent on the platform.

In 2026 the session became the center of the product. A session gives the model meta tools to search for and run tools at runtime, rather than loading every tool definition into context, plus a sandbox for large results; by mid-2026 both SDKs made sessions first-class and older direct execution became a legacy path. New usage-based pricing arrived in August 2026, and in October Composio Instant let agents pay per call for more than 100 paid third-party tools from a prepaid wallet, with no account at the tool’s vendor.

Why it’s built this way

Host the tools and the tokens instead of shipping libraries
OAuth consent, token storage and refresh are the parts each team otherwise rebuilds per app; running them centrally lets one Connect Link and one user ID cover every toolkit, and keeps credentials away from the model and the app.
Meta tools that search instead of a full tool list
Loading hundreds of tool schemas into a model’s context is slow and confuses it, so a session exposes a small fixed set of tools to discover, authenticate and execute others at runtime.
Clarity over simplicity in naming
Composio’s v3 SDK post admits its earlier names collided (is an “integration” the app or one configuration of it?), so it renamed actions, apps, integrations and connections to tools, toolkits, auth configs and connected accounts.
Bill per tool call, with search free
Pricing follows what the platform runs: each tool execution counts once, while meta tools such as tool search cost nothing, so letting the model look around is not penalized.

Timeline

  1. 2023

    Founded by Soham Ganatra and Karan Vaidya

  2. 2024

    ComposioHQ/composio repository created on GitHub in February

  3. 2025

    New v3 Python and TypeScript SDKs released in preview, with renamed concepts

  4. 2025

    $29 million in funding announced on 22 July

  5. 2026

    REST API v3.1 makes the latest tool versions the default in April

  6. 2026

    Sessions become first-class in both SDKs in June; usage-based pricing from August

  7. 2026

    Composio Instant lets agents pay per call for third-party tools in October

Sources10 · facts checked 13 October 2026

Improve this page on GitHub