Composio

license

MIT(OSI, SDK/core public on GitHub)

source

public(Python + TypeScript SDKs)

managed-tier

Composio hosted platform + Rube MCP server (auth, hosted tool execution) is the commercial layer

core-gated

gated(the execution engine is in no public repo. The MIT tree is SDKs and provider adapters only and toolkit execution the app catalog and managed OAuth all run on the hosted platform at backend.composio.dev behind a COMPOSIO_API_KEY with no self-host option documented)

The SDK and core are MIT and public, while the hosted multi-app integration and auth platform is the proprietary tier - classic open core. The gate is not a directory but an absence: the execution engine is in no public repository. What is published is SDKs and provider adapters - python/composio with its providers/, and ts/packages/ holding core, cli, cli-local-tools, cli-keyring, providers, slim, experimental and the schema converters. Toolkit execution, the catalogue of more than 1000 apps and managed OAuth all run on Composio's own servers: the README's first instruction is to "Grab a COMPOSIO_API_KEY from the dashboard first", sessions are created against the hosted API, the docs give the REST base URL as https://backend.composio.dev/api/v3.1 and describe Composio-managed auth as the default, and no self-hosting or on-premise option is documented anywhere. Nothing in the published source executes a toolkit without that platform. The finding rests on that evidence in the code, not on the mere fact that Composio sells a hosted platform.

• https://github.com/ComposioHQ/composio recorded 2026-06-04

  MIT LICENSE, public SDK source, 1000+ toolkits, ~28.6k stars

• https://raw.githubusercontent.com/ComposioHQ/composio/next/README.md recorded 2026-08-12

  "Create a session for a user, hand its tools to your agent, and let the agent take action across 1000+ apps. Grab a COMPOSIO_API_KEY from the dashboard (dashboard.composio.dev/settings) first." Also offers a hosted MCP endpoint per session - "Pass mcp: true to composio.create() and point Claude, Cursor, or any MCP client at session.mcp.url". Every path to running a tool goes through the hosted platform and a key issued by it.

• https://api.github.com/repos/ComposioHQ/composio/contents/ts/packages recorded 2026-08-12

  The published TypeScript tree is client-side only: cli, cli-keyring, cli-local-tools, core, experimental, json-schema-to-effect-schema, json-schema-to-zod, providers, slim, ts-builders. The python/ tree is the same shape - composio plus providers. There is no server, no toolkit runtime and no auth service anywhere in the repository, which is the functionality the paid platform holds.

• https://docs.composio.dev/docs/welcome recorded 2026-08-12

  Documents the REST API served at https://backend.composio.dev/api/v3.1, "Composio-managed auth" as the default in which "the agent connects accounts at runtime through the session", and session creation via composio.create(user_id) against that hosted API. No self-hosting or on-premise deployment option is documented anywhere in it.

• https://api.github.com/repos/ComposioHQ/composio recorded 2026-08-12

  Repo metadata: license spdx_id MIT, default branch next, 29,636 stars, not archived. The published tree is the SDK monorepo - python/ and ts/ - which is what `source: public` refers to; it is not the tool-execution platform, which is not published anywhere.