documentation
03 dashboard

Composio

The Composio page is the browsable catalog of third-party SaaS toolkits — Gmail, Slack, Linear, HubSpot, and a hundred more — installable with one click. One API key, every action on the catalog, surfaced to the agents you grant access to.

What this page is for

This is the UI walkthrough. For the conceptual setup and governance guide, start at Integrations → Composio.

Open /integrations/composio in the dashboard. You’ll see:

  • Header with the toolkit count and API-key status
  • Search and category filter toolbar
  • Grid of toolkit cards — name, description, category, action count, current status

Layout

Header strip

At the top, the count of available toolkits is shown, along with the Composio API key status:

  • Green dot, “API key configured” — you’re ready to install
  • Yellow dot, “API key missing” — configure one from Settings → Providers before you can install

Search and filter

The toolbar supports:

  • Search — free-text search across toolkit names, actions, and categories. Type email to find every email-adjacent toolkit
  • Category pills — “All” by default, plus one pill per category Composio publishes. Click a pill to filter

Search and category filter compose — typing in the search box while a category is active narrows within that category.

Toolkit cards

Each card shows:

  • Name and optional ★ Featured badge (toolkits Composio highlights as core)
  • Category — tiny caps above the name
  • Description — what the toolkit does
  • Action count — 12 actions, meaning how many distinct tools this toolkit exposes
  • Status pill — Available, Installed, or Blocked

Cards are sorted featured-first, then alphabetical.

Common tasks

Find a toolkit

Type in the search box. Results narrow live. Search covers toolkit name, description, individual action names, and category. If you know what you want but aren’t sure of the exact spelling, search is lenient.

Alternatively, pick a category pill (email, calendar, crm, support, dev, communication, etc.) and scroll.

Install a toolkit

  1. Find the toolkit you want
  2. Confirm the card shows Available (not Blocked — see Governance below)
  3. Click Install
  4. Wait a second for Composio to provision the endpoint

The toolkit’s status changes to Installed with a green accent. The Install button is replaced with Manage access and Uninstall.

Grant agents access

Click Manage access on an installed toolkit. You land on /mcp-installed/{id}/access — the per-agent access editor. Tick the agents that should see this toolkit’s actions. Untick to remove access.

By default an installed toolkit is not granted to any agent. This is intentional — install is one action, access is a second. It gives admins a chance to review and decide before the tools go live.

Uninstall a toolkit

Click Uninstall on the installed card. Confirm. The Composio endpoint is removed, all agent access rows are cleared, and the card reverts to Available.

Uninstall is a full removal — any access grants are lost. If you reinstall later, you’ll need to grant access again.

Blocked toolkits

If a toolkit is Blocked in Settings → Security → Composio Governance, its card shows a Blocked status pill with a greyed-out appearance. The install button is replaced by a short reason (“Blocked by policy” or similar). The toolkit can’t be installed until the block is lifted.

Similarly, if the workspace has Enforce toolkit allowlist on and the toolkit isn’t in the allowed list, it’s Blocked too — same visual treatment, different reason (“Not in allowlist”).

API-key-missing state

If no Composio API key is configured, the header shows the yellow “API key missing” status and every toolkit’s Install button is disabled with an “API key required” label. Configure the key from Settings → Providers and the page becomes functional.

Flash messages

After install or uninstall, a flash message at the top of the page confirms success or reports an error:

  • Success — green banner like “Installed Gmail. Configure per-agent access to make actions available.”
  • Failure — red banner with the provider’s error message

Failed installs are usually caused by:

  • API key invalid or expired
  • Composio service temporarily unavailable
  • The toolkit requires OAuth with the underlying service and the auth flow hasn’t completed

Common pitfalls

Clicking Install and assuming an agent can use it. Install surfaces the toolkit; access makes it available to specific agents. Without the access grant, nothing happens — the toolkit is dormant.

Installing toolkits your workspace policy blocks. If allowlist enforcement is on and you install into the allowlist but the toolkit you want isn’t in it, the card shows Blocked. Add the toolkit to the allowed list under Settings → Security, then come back here to install.

Leaving installed toolkits you no longer use. Unused Composio installations don’t cost money (per-call billing only), but they’re clutter and a potential surface. Uninstall when you’re done with them.

Treating Composio like a local MCP. Composio actions run on Composio’s cloud — they’re subject to Composio’s rate limits and availability. For mission-critical work, have a fallback.

Where to go next