Harness Hub
All startups

Composio

The integration layer: hundreds of managed tools your agents can call.

Composio handles auth, schemas, observability and reliability for the external SaaS tools an agent uses — 'plumbing for agentic actions' across Slack, GitHub, Salesforce and 250+ other surfaces.

Pros & cons

Each point cites its sources and says what kind of evidence backs it. A second reviewer tried to refute every claim before it was kept.

Pros

  • User reportsManaged OAuth makes it quick to connect agents to apps such as Gmail, Google services and Calendly; builders use it for exactly that.[1][2]
  • User reportsLarge catalog: a former Composio engineer cites auth across 1000+ apps and SDKs with more than 1M weekly npm downloads.[1]
  • User reportsAgent hosting platforms offer it as a managed MCP connector.[1]
  • MetadataThe MIT-licensed SDK repo is very active (about 30.8k stars, commits on 29 Oct 2026).[1]

Cons

  • User reportsUsers point out that once an agent is broadly connected, there is little audit of what it did or whether calls stayed in scope; competitors pitch finer-grained permissions.[1][2]
  • User reportsAccording to a competitor's co-founder, the backend cannot be self-hosted and only the client is open source.[1][2]
  • User reportsIntegration breakages have been reported, such as the Mastra provider's getTools failing and regenerated Connect MCP keys returning 401 (both issues are now closed).[1][2]
  • User reports'Self-hosted' agent stacks that use Composio still depend on its external service and API keys.[1]
Best for
Agent builders who need many SaaS integrations with managed OAuth, fast.
Watch out for
Scope permissions tightly and add your own audit logging, because the backend is SaaS-only.

Assessed Oct 29, 2026 · adversarially reviewedSuggest a correction

People

Co-founder & CEO

MCP & tools · Skills, plugins & mods

Open roles (30)

All 30 roles

Their open-source work

ComposioHQ/composio

Integration layer and toolset for AI agents.

Maintained by Composio

@composio/cli@0.6.3released
4 pros · 3 cons

Activity

Last push
· today
Latest release
@composio/cli@0.6.3
· yesterday
Last 90 days
20+ releases
  1. @composio/cli@0.6.4-beta.573CLI Beta @composio/cli@0.6.4-beta.573Pre-release

    · yesterday

    What's Changed docs: update toolkits, API spec, and meta tools data by @sdkrelease[bot] in https://github.com/ComposioHQ/composio/pull/5479 docs: reconcile polling, proxy permissions, and SDK examples by @olearycrew in https://github.com/ComposioHQ/composio/pull/5476 docs:…

  2. @composio/cli@0.6.3CLI @composio/cli@0.6.3

    · yesterday

    Patch Changes Update @composio/client to 2.1.36 to include the latest API changes. Release archives now include a release-manifest.json that lists the support files they ship. composio upgrade installs exactly what the manifest lists, so later releases can drop a support file…

  3. @composio/cli@0.6.3-beta.571CLI Beta @composio/cli@0.6.3-beta.571Pre-release

    · 2d ago

    What's Changed fix(toolchain): lock mise tools for windows-x64 by @jkomyno in https://github.com/ComposioHQ/composio/pull/5475 Full Changelog: https://github.com/ComposioHQ/composio/compare/@composio/cli@0.6.3-beta.570...@composio/cli@0.6.3-beta.571

  4. @composio/cli@0.6.3-beta.570CLI Beta @composio/cli@0.6.3-beta.570Pre-release

    · 2d ago

    What's Changed docs: update guides for SDK changes by @sdkrelease[bot] in https://github.com/ComposioHQ/composio/pull/5473 fix(cli): proxy reads stdin only with -d -, execute fails on a silent stdin pipe by @composio-zen[bot] in https://github.com/ComposioHQ/composio/pull/5466…

  5. @composio/cli@0.6.3-beta.569CLI Beta @composio/cli@0.6.3-beta.569Pre-release

    · 2d ago

    What's Changed chore(sdk): update composio-client to 2.1.36 by @sdkrelease[bot] in https://github.com/ComposioHQ/composio/pull/5471 Full Changelog: https://github.com/ComposioHQ/composio/compare/@composio/cli@0.6.3-beta.568...@composio/cli@0.6.3-beta.569

Checked against GitHub on Nov 21, 2026. Release notes are shortened to plain text.

On X

Posts by the company and its team, shown as plain text; “Load on X” loads X's script for that post, which may set cookies.

  • We ran Kimi K3 through 3 more agent harnesses (Pi Agent, OpenCode, and Codex) bringing the comparison to 6 harnesses across 26 agentic tasks.

    2 things stood out: Codex ranked last on success despite mid-pack speed and cost, while Claude Code cost about 4x more than Hermes. 🧵🧵 pic.twitter.com/8YLOE1C0yZ

    Open on X

Follow @composio on X · The X feed

A registry and toolchain for MCP servers.

Smithery indexes and helps deploy MCP (Model Context Protocol) servers — a distribution layer for the tool ecosystem agents connect to.

3 pros · 4 cons

Exa

Search API purpose-built for AI agents.

Exa (formerly Metaphor) provides neural search and web-crawl APIs tuned for agent consumption — live, cited knowledge for agents instead of stale training data.

4 pros · 4 cons

Search and extraction API optimized for LLMs and agents.

Tavily gives agents a single API for search, crawling and in-depth extraction, returning clean, cited results — a common tool in research-agent harnesses.

4 pros · 4 cons

Connections

Relations from the Harness Hub knowledge graph, as charted in the State of Harness reports.

Maintains · 1

Built on · 1

Similar entries · 6

The Harness Hub newsletter

New harness companies, projects, releases and the monthly State of Harness report, in your inbox.