Composio

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-09-07. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://connect.composio.dev/mcp ; https://docs.composio.dev/docs/single-toolkit-mcp (redirect correction 2026-08-28: the address previously recorded here, docs.composio.dev/mcp/overview, 308s to this one and this one returns 200) ; repo https://github.com/ComposioHQ/GHMCP

• https://connect.composio.dev/mcp
• https://docs.composio.dev/docs/single-toolkit-mcp
• https://github.com/ComposioHQ/GHMCP

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

Recorded by the harvest: a small fixed meta-tool set plus the customer's own connected toolkits

• COMPOSIO_GET_TOOL_SCHEMAS
  Retrieves schema definitions for specified tools to validate their input/output structure.
  evidence: in the vendor docs · calling it reads · required: tool_slugs · read off composio, an aggregator wrapping the vendor's API rather than the vendor's own server
• COMPOSIO_MANAGE_CONNECTIONS
  Checks or connects toolkits by slug so the agent can authenticate before calling their tools.
  evidence: in the vendor docs · calling it reads · required: toolkits · read off composio, an aggregator wrapping the vendor's API rather than the vendor's own server
• COMPOSIO_MULTI_EXECUTE_TOOL
  Executes multiple logically independent tools in parallel with consolidated response tracking.
  evidence: in the vendor docs · calling it reads · required: tools, tool_slug, arguments, sync_response_to_workbench · read off composio, an aggregator wrapping the vendor's API rather than the vendor's own server
• COMPOSIO_REMOTE_BASH_TOOL
  Executes bash commands in a sandbox environment with a 3-minute execution limit.
  evidence: in the vendor docs · calling it reads · required: command · read off composio, an aggregator wrapping the vendor's API rather than the vendor's own server
• COMPOSIO_REMOTE_WORKBENCH
  Executes Python code in a persistent remote Jupyter sandbox with state preservation across executions.
  evidence: in the vendor docs · calling it reads · required: code_to_execute · read off composio, an aggregator wrapping the vendor's API rather than the vendor's own server
• COMPOSIO_SEARCH_TOOLS
  Processes structured English search queries to discover and return relevant tools from Composio's toolkit ecosystem in parallel.
  evidence: in the vendor docs · calling it reads · required: queries, session · read off composio, an aggregator wrapping the vendor's API rather than the vendor's own server

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

Install, as the source shows it:

curl -fsSL https://composio.dev/install | bash

quoted from https://composio.dev/cli on 2026-09-27, via shell

curl -fsSL https://composio.dev/install | sh

quoted from https://docs.composio.dev/docs/cli on 2026-09-27, via shell

curl -fsSL https://composio.dev/install | sh -s -- @composio/cli@0.3.1

quoted from https://docs.composio.dev/docs/cli on 2026-09-27, via shell

Login or key hint seen on the page:

composio login --agent

Subcommands seen with the binary:

dev, execute, generate, link, links, login, proxy, run, search, setup, start, upgrade

Where it was documented:

• https://composio.dev/cli (the page that documented the CLI)

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

api_gate, verbatim from the file:

free (100K tool calls/mo, 50K trigger events/mo, unlimited connections on the Free plan, no credit card)

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/ComposioHQ/GHMCP

github.com/ComposioHQ tied to the vendor by rule 2, account website https://composio.dev has the vendor's domain, confidence strong

The five most recently pushed, on 2026-09-08:

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

• Proxy tool calls to SaaS apps

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

• https://composio.dev
• https://composio.dev/pricing
• https://docs.composio.dev/docs/single-toolkit-mcp
• https://github.com/ComposioHQ/GHMCP
• https://connect.composio.dev/mcp

5 source URLs. Raw sources field, verbatim:

https://composio.dev, https://composio.dev/pricing, https://docs.composio.dev/docs/single-toolkit-mcp, https://github.com/ComposioHQ/GHMCP, https://connect.composio.dev/mcp

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.