Monorepo · established

ComposioHQ/composio

Agent-integration platform and SDK monorepo providing toolkits, tool search, per-user authentication, sessions, triggers, and a sandboxed workbench across TypeScript and Python agent frameworks.

agent integrationsauthenticationtool execution
Installation GuideInstruction Manual

What it contains

TypeScript and Python SDKs, provider adapters, a standalone CLI, a large hosted toolkit catalog, connection management, tool routing, triggers, and sandbox/workbench features.

Typical uses

Give an AI application authenticated, user-scoped actions in external SaaS products without hand-building every OAuth and tool adapter.

Why people choose it

Choose it when an agent must act across many third-party services and connection management is a bigger problem than the underlying model call.

License
MIT
Maintenance
active
Latest release
See GitHub Releases
Last meaningful update
2026-08-18
Maturity
established
Production readiness
production

Classification

Subject domains

agent integrationsauthenticationtool execution

Task categories

connect accountssearch toolsexecute actionshandle triggers

Project phases

architectureimplementationdeploymentoperations

Secondary types

SDKCLIhosted service

Select when

  • Need authenticated agent actions across many SaaS applications
  • Need per-user connection and session boundaries
  • Need the same tool layer across several agent frameworks

Do not select when

  • No external service may receive data or actions
  • Only one simple API integration is required
  • Cannot rely on a hosted integration control plane
Implementation complexity
high
Setup effort
medium
Learning curve
medium
Confidence
high

Routing heuristic 86.0%

Routing specificity
5/5
Setup simplicity
4/5
Operational maturity
5/5
Composability
5/5
Local control
3/5
Security boundary clarity
4/5
First-party routing documentation
5/5

Strengths

  • Large toolkit surface
  • First-party TypeScript and Python SDKs
  • Provider adapters reduce framework-specific glue

Poor-fit scenarios

  • No external service may receive data or actions
  • Only one simple API integration is required
  • Cannot rely on a hosted integration control plane

Limitations

  • Hosted accounts, connected credentials, billing, and service availability become dependencies
  • Broad tool access increases authorization risk
  • The monorepo changes quickly
ts/packages/core/

Discover toolkits, create user-scoped sessions, retrieve tools, and execute actions from TypeScript.

TypeScriptsessions
ts/packages/slim/

Use the same core API with a smaller package that omits bundled source and documentation.

TypeScriptsmaller package
python/composio/

Use Composio sessions, tools, authentication, and execution from Python applications.

Pythonsessions
ts/packages/cli/

Search, link, execute, and script toolkit operations from a terminal or coding agent.

CLIlocal tools
Provider adapters adapter collection
ts/packages/providers/ and python/providers/

Translate Composio tools into the native tool format of supported agent frameworks.

framework adapters
hosted toolkit catalog

Find a small relevant subset of actions from the hosted catalog instead of loading every available schema.

tool discovery
Connected accounts authentication service
hosted connection layer

Link and manage user-specific OAuth or API-key connections for external services.

OAuthidentity
Triggers event service
hosted trigger layer

Subscribe to supported external events and deliver them to an agent application.

eventswebhooks
hosted workbench

Give an agent a controlled environment for files, scripts, and longer-running tool workflows.

sandboxfiles
Languages
TypeScript, Python
Frameworks
OpenAI Agents, Claude Agent SDK, Vercel AI SDK, LangChain, LangGraph, CrewAI, AutoGen, and others
Runtimes
Node.js 22+ and Python 3.10+
Operating systems
macOS, Linux, Windows
Installation methods
npm/pnpm packages, pip packages, or Composio CLI installer
Interfaces
TypeScript SDK, Python SDK, CLI, remote tools/MCP-style surfaces, web dashboard
Required credentials
Composio account/API key plus user-scoped connected-service authorization
External services
Composio and each connected toolkit provider
Hardware
No special hardware
Major dependencies
Selected SDK/provider adapter and agent framework

Compatibility notes

Apple silicon is suitable. Install only the SDK and provider adapter your app actually uses, and inspect the shell installer before using the standalone CLI route.

One-sentence semantic summary

Agent-integration platform and SDK monorepo providing toolkits, tool search, per-user authentication, sessions, triggers, and a sandboxed workbench across TypeScript and Python agent frameworks.

Capability keywords

ComposiotoolkitsOAuthagent toolssessionstriggerssandbox

User intent phrases

  • Need one integration layer for many agent tools
  • Need user-scoped authentication for agent actions

Negative match phrases

  • Require fully local offline integrations
  • Need only one direct API

Differentiators

Combines a broad tool catalog with per-user authentication, framework adapters, tool search, and execution infrastructure.

Security considerations

Connected accounts can authorize consequential external actions. Use narrow scopes, bind every session to the correct user, validate tool arguments, and add approval for destructive or financial operations.

Privacy considerations

Prompts, tool arguments, files, and provider responses may traverse Composio and connected services. Review each party's retention, region, and subprocessors before production use.

Uncertainty

Unresolved items

None documented.

Inference notes

Routing guidance is an analyst synthesis based on the first-party repository and README.

Evidence

  • repository_metadata · Repository identity and current GitHub metadata checked on August 18, 2026.
  • readme · Primary first-party README inspected.

Repository usage guidance

installation summary
Install @composio/core plus one provider adapter, or the equivalent Python packages; use the CLI for local agent-facing workflows
basic usage summary
Create a user-scoped session, link the required account, search/select the smallest tools, and execute with validation and approvals
documented entry points
Composio SDK classes and composio CLI
key configuration files
Environment variables and application connection/session configuration
important directories
ts/, python/, docs/
documentation paths
README.md, INSTALL.md, docs.composio.dev
example paths
SDK quickstarts in README.md

Relationships

overlapping
medium
Both connect many external services. Composio is an agent SDK and auth/tool layer; n8n is a visual workflow automation platform.

Recommended combinations

Use Composio as the authenticated tool boundary under a clearly defined agent workflow; use n8n only when a visual, deterministic orchestration layer adds distinct value.

Routing rules

rule_054: Need authenticated actions across many SaaS tools for an AI agent P946

Rationale

Agent-integration platform and SDK monorepo providing toolkits, tool search, per-user authentication, sessions, triggers, and a sandboxed workbench across TypeScript and Python agent frameworks.

Required conditions

Need authenticated agent actions across many SaaS applications

Preferred

ComposioHQ/composio

Fallback

Choose the closest narrowly scoped existing repository only after comparing permissions and workflow ownership.