# Composio: Pre-Authenticated Toolkits and Session Management for AI Agents

> Composio is an open-source SDK monorepo that gives AI agents over 1,000 pre-authenticated toolkits, per-user sessions, and provider adapters for frameworks such as OpenAI Agents, Claude Agent SDK, LangChain, and Vercel AI SDK. Each session scopes app connections to one user and exposes tools ready for the agent to call.

**ComposioHQ/composio** — Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

- Repository: https://github.com/ComposioHQ/composio
- Website: https://docs.composio.dev
- Stars: 30,331 · Forks: 4,830
- Language: TypeScript
- License: MIT
- Published: 2026-08-08 · Updated: 2026-08-18 · Language: en
- Canonical page: https://hysenlabs.com/projects/composiohq-composio

## What Composio Solves for AI Agent Builders

Building an AI agent that acts on a user's behalf across external apps requires solving two problems: connecting to each app's API and managing per-user credentials. Doing that for dozens of apps is a significant engineering investment. Composio addresses both problems with a session model that scopes app connections to a single user and a toolkit catalog that ships pre-authenticated integrations for over 1,000 apps.

The README describes the goal as giving agents "1000+ pre-authenticated toolkits, per-user sessions, authentication, triggers, and a sandbox, so you can ship agents that turn intent into action." The typical user is a developer building an AI agent that needs to summarize emails, create calendar events, push code, or interact with a CRM on a specific user's behalf.

## Sessions, Tool Discovery, and the Context Management Model

The central abstraction is a session. A session is created for a user identifier, connects to that user's authenticated accounts, and returns a tools object ready for injection into an agent. The README explains: "Each session is scoped to one of your users."

By default a session provides meta tools that discover, authenticate, and execute app tools at runtime, so the agent does not load hundreds of tool definitions into its context window at startup. The session_id can be stored and reused across turns with composio.use(), maintaining continuity across a multi-turn conversation.

Each session also exposes a hosted MCP endpoint. Passing mcp: true to composio.create() and pointing any MCP client at session.mcp.url connects Claude, Cursor, or another MCP-compatible tool to the session's tools. This means the same session works with both programmatic agent frameworks and MCP-based tools without code changes.

## Getting Started with TypeScript and Python

For TypeScript with OpenAI Agents:

```bash
npm install @composio/core @composio/openai-agents @openai/agents
```

For Python with the same provider:

```bash
pip install composio composio-openai-agents openai-agents
```

Both SDK packages expose the same session API. Create a Composio instance, create a session for a user, retrieve the tools, and pass them to the agent framework's tool parameter:

```typescript
const composio = new Composio({ provider: new OpenAIAgentsProvider() });
const session = await composio.create("user_123");
const tools = await session.tools();
```

The README notes that @composio/core intentionally packages its TypeScript source and SDK documentation so that coding agents can inspect the installed package. A smaller @composio/slim package provides the same API without the bundled source.

## Provider Adapters and Framework Support

Composio ships provider adapters that translate its tools into the native tool format expected by each agent framework. The README lists adapters for OpenAI, OpenAI Agents, Anthropic, Claude Agent SDK, Vercel AI SDK, Google GenAI, Google ADK, LangChain, LangGraph, LlamaIndex, Mastra, Cloudflare Workers AI, TypeSafe (Jev), CrewAI, and AutoGen. Each adapter is a separate package, so teams only install what they use.

For frameworks not in the list, the README documents a custom provider path and an MCP fallback for any MCP-compatible client. The Pi provider exists as an experimental package in @composio/experimental.

## The Composio CLI for Shell and Coding Agent Use

The CLI installs separately and provides a local tool surface for shell use and coding agents:

```bash
curl -fsSL https://composio.dev/install | sh
```

After installation, run composio login to authenticate. The README documents four primary commands: composio search to find tools, composio execute to run them, composio link to connect accounts, and composio run to script workflows in TypeScript.

The package.json shows the CLI package as @composio/cli with a build:binary target, indicating it ships as a standalone binary. The README specifies that COMPOSIO_INSTALL_SHELL=none suppresses shell configuration changes during install-only runs.

## Limitations and What to Verify Before Committing

Composio requires a COMPOSIO_API_KEY from the dashboard. This creates a dependency on the Composio cloud service for session management and authentication, even when the agent code runs entirely on the developer's infrastructure. The README documents the hosted MCP endpoint as a session feature, which also relies on the cloud service.

The recent releases in the repository are all labeled CLI Beta (for example, @composio/cli@0.4.2-beta.406). This signals that the CLI API may change. The Python SDK pyproject.toml shows composio==1.0.0rc6 in the dev dependencies, indicating the Python SDK was also at a release candidate stage.

Teams with strict data residency requirements should evaluate whether routing user credentials and tool invocations through Composio's cloud service is acceptable. The README does not document a fully self-hosted deployment path for the session management layer.

## License and Maintenance

The repository is licensed under MIT, which permits unrestricted use in commercial and open-source products. The monorepo contains both the TypeScript SDK (in ts/packages/) and the Python SDK (in python/) with providers in python/providers/. The package.json lists turbo as the build orchestrator and pnpm as the package manager.

The last push to the repository was on 2026-09-26. Recent releases have shipped daily, all as CLI beta versions. The core SDK packages (@composio/core, composio Python) appear on a separate release cadence from the CLI. The repository includes a CHANGELOG.md and a parity-variance.json, suggesting the team tracks feature parity between the TypeScript and Python SDKs.

## Conclusion

Composio is a strong fit for teams building multi-tenant AI agents that need to act on behalf of individual users across many SaaS apps. The session model and schema-validated tool results reduce integration overhead significantly. Verify the authentication flow for your target apps before committing: not all toolkits behave identically across providers, and the CLI beta label on recent releases signals that the API is still evolving.

## FAQ

### What is Composio used for?

Composio provides pre-authenticated toolkits and per-user sessions for AI agents, letting agents act on behalf of individual users across over 1,000 apps including email, calendar, code repositories, and CRM systems.

### Is Composio free to use?

The README does not document pricing in the repository itself; a COMPOSIO_API_KEY is required from the Composio dashboard. Check the pricing page at composio.dev for current plan details.

### How do I use Composio with Claude?

Install the Anthropic provider package and pass it to the Composio constructor. For TypeScript use @composio/anthropic; for Python use composio-anthropic. The Claude Agent SDK has its own adapter (@composio/claude-agent-sdk and composio-claude-agent-sdk).

### How do I install the Composio CLI?

Run `curl -fsSL https://composio.dev/install | sh` on macOS or Linux. After installation open a new terminal and run `composio login`. The README notes COMPOSIO_INSTALL_SHELL=none for install-only runs that skip shell configuration.

## Sources

- [Official documentation](https://docs.composio.dev)
- [Official README](https://github.com/ComposioHQ/composio#readme)
- [Project repository](https://github.com/ComposioHQ/composio)
- [Release notes](https://github.com/ComposioHQ/composio/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/composiohq-composio