composio
Composio is an integration platform that gives AI agents and LLMs authenticated access to hundreds of external tools and apps (Gmail, Slack, GitHub, etc.) through a managed SDK, handling OAuth, auth config, and tool execution so agents can take real-world actions.
Embed badge
[](https://opensources.dev/resource/composio)MITPermissive — free to use in commercial and proprietary software, with attribution.View license →
Production readiness
4/5- Actively maintainedCommits in the last 6 months
- No known vulnerabilitiesNot yet scanned
- Clear, usable licenseMIT (permissive)
- Proven adoptionWidely used
- Has documentationDocumentation indexed
npm install composioOur analysis
Composio is a tool-and-integration layer for AI agents, providing managed connectors to hundreds of third-party SaaS apps along with the auth (OAuth, API keys) and execution plumbing needed for LLMs to invoke them. It exposes these as function-calling tools across multiple agent frameworks and SDKs.
When to use composio
Use it when building agents that need to act on external services (send emails, create tickets, post to Slack) and you want to avoid hand-rolling OAuth flows and per-app API wrappers. It's a strong fit for production agents needing many integrations with managed authentication and token refresh.
When not to
If you only need a couple of simple API calls, a self-hosted tool registry, or you're standardizing on open protocols like MCP without a managed vendor, the dependency and hosted-service model may be overkill. It's also not an agent orchestration/reasoning framework itself — pair it with LangChain, CrewAI, or your own loop.
Strengths
- Large catalog of pre-built, authenticated integrations removes significant boilerplate
- Handles OAuth/auth config and credential management as a managed service
- Framework-agnostic with Python and TypeScript SDKs and adapters for major agent frameworks
- Type-checked docs (Twoslash) suggest active attention to SDK/docs accuracy
Trade-offs
- Managed/hosted model creates vendor dependency for auth and tool execution
- Quality and freshness varies across the long tail of integrations
- Adds an abstraction layer that can obscure the underlying API behavior
- Not a reasoning/orchestration framework — you still need agent logic elsewhere
Maturity
Widely adopted (28k+ stars) with an actively maintained, multi-language SDK and polished documentation tooling. It is a commercial open-source product backed by a company, so longevity is tied to that business but the project shows strong momentum.
Composio Docs
Documentation site for Composio, built with Fumadocs.
Getting Started
bun install
bun run dev
Open http://localhost:3000.
Project Structure
docs/
├── app/ # Next.js app router
├── content/ # MDX content
│ ├── docs/
│ ├── examples/
│ ├── changelog/
│ └── reference/
├── components/ # React components
├── lib/ # Utilities
└── public/ # Static assets
Adding Content
Create an .mdx file in content/, add frontmatter, then add to meta.json:
---
title: Page Title
description: Brief description
---
Content here...
Components
<Tabs items={['Python', 'TypeScript']}>
<Tab value="Python">...</Tab>
<Tab value="TypeScript">...</Tab>
</Tabs>
<Callout type="info">Note</Callout>
<Cards>
<Card title="Title" href="/path" />
</Cards>
Sidebar
Each folder has meta.json for ordering:
{
"pages": ["page-one", "page-two"]
}
TypeScript Code Blocks
All TypeScript code blocks in MDX files are type-checked at build time using Twoslash. This ensures docs stay in sync with the SDK.
Use
// @noErrorsto skip checking for partial snippetsUse
// ---cut---to hide setup code from outputRun
bun run buildlocally to validate before pushing
See CLAUDE.md for detailed patterns and troubleshooting.
Search
Docs search uses Algolia when NEXT_PUBLIC_ALGOLIA_SEARCH_API_KEY is set; otherwise it falls back to the local Fumadocs /api/search endpoint for development and tests. The sync script builds a first-party index from MDX/OpenAPI/toolkit data (no crawler required), splits long pages into section-sized records, configures searchable attributes/custom ranking/distinct, requests clickAnalytics, and sends search result view/click events with search-insights.
NEXT_PUBLIC_ALGOLIA_APP_ID=62HI9PQZ1L # optional; default shown
NEXT_PUBLIC_ALGOLIA_SEARCH_API_KEY=...
NEXT_PUBLIC_ALGOLIA_INDEX_NAME=docs_composio_dev_62hi9pqz1l_pages # optional; default shown
Sync the Algolia index with an admin key:
ALGOLIA_APP_ID=62HI9PQZ1L
ALGOLIA_ADMIN_API_KEY=...
ALGOLIA_INDEX_NAME=docs_composio_dev_62hi9pqz1l_pages bun run sync:search
Preview the generated records or test live relevance:
bun run sync:search --dry-run --samples
ALGOLIA_SEARCH_API_KEY=... bun run test:search "oauth auth config" "gmail send email"
Commands
CommandDescriptionbun run devDev serverbun run buildProduction build (validates TS code blocks)bun run types:checkType checkbun run sync:searchSync docs search records to Algoliabun run test:searchQuery the configured Algolia index from the terminal