Skip to content
My Agent Platform

Composio (250+ apps)

Composio is a tool-aggregation service that gives your agent access to 250+ third-party apps — Notion, Slack workspaces, GitHub, Linear, HubSpot, Salesforce, Airtable, Jira, Asana, and many more — through a single key. You manage which apps are connected on Composio’s side (where they handle the OAuth flows); we just need your Consumer API key so your agent can call those tools on your behalf.

This is bring-your-own-key (BYOK). The platform doesn’t depend on Composio; it’s an optional extension if you want broader app coverage than what we connect directly.

Why Composio?

Section titled “Why Composio?”

We connect to Gmail, Outlook, calendars, Telegram, Discord, Slack, the major social networks, and Follow Up Boss directly — no aggregator in the middle. Direct connections are faster, more reliable, and don’t depend on a third-party uptime.

But that’s a few dozen integrations. If you want your agent to also create a Notion page, file a Linear ticket, post to a specific Slack channel in your team workspace, or update a HubSpot deal — those aren’t worth us building one-by-one. Composio already has them all, with maintained auth flows. Hand your agent the key and it can use them.

Setting it up (2 minutes)

Section titled “Setting it up (2 minutes)”

  1. Sign up at Composio if you haven’t already.

  2. Connect the apps you want on Composio’s dashboard — they handle the OAuth UI for each one.

  3. Find your Consumer API key. On the Composio install / connect page you’ll see a block that looks like:

    MCP URL          https://connect.composio.dev/mcp
    x-consumer-api-key  ck_u••••••••••••

    The value next to x-consumer-api-key (it starts with ck_) is the key we need. Click to reveal/copy it.

  4. Paste it into Settings → Integrations → Composio on My Agent Platform.

  5. We’ll validate it against Composio (we round-trip a minimal MCP handshake to connect.composio.dev/mcp), then store it encrypted at rest. We never display the key back to you — only a masked tail.

  6. Restart your agent from Settings → Agent so the new key takes effect.

Add or remove apps any time from your Composio account — your agent discovers what’s connected at runtime, so no sync step is needed on our side.

What if Composio rejects my key?

Section titled “What if Composio rejects my key?”

If validation fails, the card shows the exact error from Composio plus a “Save without checking” button. Use it if you’re confident the key is correct but the validation round-trip is misbehaving (a transient Composio outage, a header proxy issue, etc.). The key is stored as-is; the agent will surface any real failures at the time it tries to call a tool.

The most common cause of a “rejected” error is pasting the wrong key — Composio’s UI has historically shown several different keys at different points (developer keys starting with ak_, project keys, etc.). The only one that works for the consumer / MCP surface is the one labeled x-consumer-api-key on the install page; it starts with ck_.

What happens if I disconnect?

Section titled “What happens if I disconnect?”

Disconnect deactivates the key immediately — the agent loses access on its next restart. Your Composio account itself is untouched; the apps you’ve connected on Composio’s side stay connected, you just stop letting our platform’s agent use them. The encrypted key blob is retained briefly for one upgrade cycle in case you change your mind, then hard-deleted.

What we do not see

Section titled “What we do not see”

We see only the Consumer API key you paste. We never see:

  • Which apps you have connected on Composio (the agent discovers them at runtime)
  • The OAuth tokens for those apps (they live on Composio’s side; the agent never touches them)
  • Any payload your agent sends or receives through Composio — those go from your agent pod directly to connect.composio.dev/mcp; we don’t proxy them

Common gotchas

Section titled “Common gotchas”
  • “Invalid consumer API key” — almost always means you pasted a different key from your Composio account. The one we need is the ck_ key shown under x-consumer-api-key on the install page. Developer keys (ak_…) won’t work here.
  • Connected, but the agent says “I don’t have Notion” — restart your agent from Settings → Agent. The Composio MCP config is injected on provision, so a running pod won’t see the new key until it restarts.
  • Restarted, still no apps — open your Composio account and confirm the app actually shows as connected there. The agent only sees apps you’ve connected on the Composio side.

Pricing

Section titled “Pricing”

Composio bills you on their side. The free plan covers 20K tool calls/month, which is plenty for most agents. We don’t add anything on top.