# Composio (API + MCP) vs MCP Gateway (slim)

> Composio scores 77.7 (BB) to MCP Gateway's 71 (BB) for tool access for agents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/composio-rube-vs-mcp-gateway-parkkola.md (~5,500 tokens) · this version ~3,530 tokens · JSON https://www.anchorterminal.com/compare/composio-rube-vs-mcp-gateway-parkkola.json · canonical https://www.anchorterminal.com/compare/composio-rube-vs-mcp-gateway-parkkola
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Composio (API + MCP) scores 77.7 (BB) on agent readiness against MCP Gateway's 71 (BB), and leads in 6 of 7 scored categories. MCP Gateway leads on reliability. Both do tool access for agents.

- Composio (API + MCP): BB 77.7, rank #21 of 1266 · https://www.anchorterminal.com/tools/composio-rube.min.md
- MCP Gateway: BB 71, rank #158 of 1266 · https://www.anchorterminal.com/tools/mcp-gateway-parkkola.min.md
- Composio (API + MCP), good for A developer whose agent acts in many apps for many end users and wants auth, tool schemas and execution handled. Ahead on Schema & documentation, 89 against 75; Agent ergonomics, 90 against 77; Payments & pricing, 60 against 30; Transparency & trust, 83 against 60. Also A hosted endpoint, with nothing to install; Open source.
- MCP Gateway, good for One person running many local and remote MCP servers who wants a single local entry with a small tool list, scoped keys and poisoning checks Ahead on Reliability, 87 against 70. Also Runs on your own machine.

| Category | Composio (API + MCP) | MCP Gateway |
| --- | --- | --- |
| Reliability (16%) | 70 | 87 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 89 | 75 |
| Agent ergonomics (13%) | 90 | 77 |
| Security & auth (14%) | 84 | 80 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 93 | 90 |
| Transparency & trust (7%) | 83 | 60 |

| Fact (where they differ) | Composio (API + MCP) | MCP Gateway |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Composio | Mikko Parkkola |
| Hosted endpoint | `https://backend.composio.dev/api/v3.1` | no (local only) |
| Transports | HTTP, Streamable HTTP | stdio, Streamable HTTP, SSE (legacy), websocket |
| Price for tool access for agents | $0.0003 per call | not published |
| Licence | MIT | PolyForm Noncommercial 1.0.0 (source-available, not OSI) for every first-party file from 4.0.0. Personal and noncommercial use is free; running it in or for a business needs a commercial licence at EUR 500 a month per named project through GitHub Sponsors. 3.0.0 to 3.2.1 shipped as MIT and stay MIT for those copies, and 3.3.x shipped a small MIT core under per-file headers |
| Tools exposed | 7 | 11 |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.ComposioHQ/composio` | `io.github.MikkoParkkola/mcp-gateway` |
| Last release | 2026-10-22 | 2026-10-06 |
| Privacy policy last updated | 2025-11-18 | no document linked |
| Terms restrict automated access | yes | not found in the text |
| Popularity | 30k stars, 1.1M npm/wk | 65 stars, 49 npm/wk |
| Agent reviews | 3.5/5 (8) | none |

Why the edge:
- Payments & pricing, Composio (API + MCP) +30: Composio (API + MCP) 60 (No x402, MPP or L402 (0). Per-unit prices public without a login, $0.0003 a tool call and $0.003 a trigger event on Pro, $0.0005 and $0.005 through Composio-managed apps, re-read on 1 November (20). Hobby has 100,000 tool calls and 50,000 triggers a month with no card, paused at the cap (20). `composio login --agent` creates an agent account and project key from the CLI with no browser or email signup, documented for unattended agents. Connecting a person's apps still needs their OAuth consent (20). 0 + 20 + 20 + 20 = 60.); MCP Gateway 30 (Self-hosted rule, scored on the paid option because any company use needs a commercial licence, as gaia and screenpipe (also noncommercial licences) were read. No payment protocol (0). The standard commercial licence is a public flat EUR 500 a month per named project through GitHub Sponsors, plan-only pricing (10). Personal and noncommercial use is free with no card or account, but there is no free route or stated evaluation period for a company (10 of 20). It installs from Homebrew, crates.io or ghcr.io with no sign-up, and an agent with a shell can run the setup wizard, but buying the licence takes a person on GitHub Sponsors, as screenpipe's did (10 of 20). 0 + 10 + 10 + 10 = 30.)
- Transparency & trust, Composio (API + MCP) +23: Composio (API + MCP) 83 (SDKs and CLI are MIT on GitHub, the platform is hosted and closed under Sampark Inc's terms (20). A retention page that matches the ZDR page, tool logs with payloads kept up to a year, and ZDR as a paid add-on. The DPA, last updated 17 October 2026, and the retention page, both re-read on 1 November, agree on deletion within 30 days of an organisation's deletion and on payloads never being used to train models, with de-identified execution metadata allowed for training and kept indefinitely (30). Rube's shutdown came with 37 days from the end of sign-ups to closure and refunds, price changes carry dates and legacy plans run to 31 December 2026, and the changelog carries dated deprecations and breaking changes, but there's no written deprecation policy (14). The DPA points to the subprocessor list in the trust centre, which renders only with JavaScript and we couldn't read, and the docs don't state hosting regions (12). 20 + 30 + 14 + 12 = 76.); MCP Gateway 60 (PolyForm Noncommercial 1.0.0, source-available and not OSI, with affirmative SPDX headers on every first-party file and LICENSES.md, NOTICE.md and COMMERCIAL.md that agree with each other and say what the earlier MIT grants still cover. Read as gaia's PolyForm source was (20 of 30). Self-hosted, so data stays where the owner runs it; secrets go to the OS keychain, files holding them are 0600 on Unix, and SECURITY.md states the Windows gap. There is no privacy statement (20 of 30). Deprecation notices with versions for the MIT 3.0.0 to 3.2.1 releases on crates.io and npm, upgrade guides for 3.0 and 4.0 and a stated support window of the latest release only, but the 3.3.0 relicence has no changelog entry, and AUTHORSHIP.md says the licensing scheme still awaits an IP lawyer's sign-off (9 of 20). No telemetry, analytics or update check found in the source; Prometheus metrics stay local behind a feature flag, and the plugin marketplace host is contacted only by plugin commands. The docs state nothing either way (15 of 20). 20 + 20 + 9 + 15 = 64.)
- Reliability, MCP Gateway +17: Composio (API + MCP) 70 (Rube itself is gone, so this grades the Composio platform that's left. Instatus page at status.composio.dev with components for the platform, triggers, third-party auth, Composio For You and Composio Connect MCP, and an RSS history (20). In the 90 days to 1 November, Composio Connect MCP returned 502s to about 19 per cent of users for 7 hours 58 minutes from 19:42 UTC on 6 October, still read as one major outage. Smaller incidents were QuickBooks rate limits on 22 August, API latency on 24 August (1 hour 29 minutes), degraded webhook triggers on 2 September (1 hour 10 minutes), platform API errors on 17 September (21 minutes), an 8-minute auth problem on 18 September, Instagram toolkit errors on 2 October (1 hour 34 minutes), the Discord Bot toolkit unavailable from 5 to 7 October and 5 minutes of platform errors on 15 October. Since 17 October, Connect links failed with "Invalid or expired link" for some end users from 05:30 to 18:05 UTC on 20 October after a new rate limit was applied too strictly, which hit one feature and so reads as partial. Latency was degraded on some endpoints for 1 hour 33 minutes on 21 October (19:34 to 21:07 UTC), Code Interpreter tool calls failed from 22 to 23 October until the toolkit was disabled, and Workday, Salesforce and Canvas triggers failed for 18 hours 55 minutes from 22 October. The platform had a 10-minute major outage on 23 October (10:39 to 10:49 UTC), partial outages of 10 minutes on 25 October and 5 minutes on 26 October, an 8-minute Tool Search incident on 26 October, and Connect MCP a 7-minute major outage on 30 October (05:20 to 05:27 UTC) after a faulty deployment. All are under an hour, so minor by our line, and the incident pages give these durations where the RSS feed says 11 hours 37 minutes and 7 hours for 25 and 30 October. One major (10). Limits per organisation per minute, 2,000 on Hobby and 10,000 on Pro, re-read on 1 November (15). 429s carry Retry-After and X-RateLimit headers, the docs say to honour it, and the SDKs (since 12 October) and CLI 0.5.0 (21 October) send executions once, with no retry after a timeout (15). No SLA published below Enterprise (0). The platform is GA, with approvals and some session policies marked experimental (10). 20 + 10 + 15 + 15 + 0 + 10 = 70.); MCP Gateway 87 (Local-package reading, as for graphicle and claude-mem, since the owner runs it. Official packages on crates.io (`cargo install mcp-gateway`), a Homebrew tap, release binaries and ghcr.io, with Rust 1.95 and macOS, Linux and Windows builds stated (20). A public CI workflow runs clippy with warnings as errors, the full test suite, fmt, cargo audit, secret scans and Helm smoke tests on pushes and pull requests, and the last eight runs on main passed by 26 October 2026 (25). Four open issues on GitHub on 2 November 2026, one a labelled bug filed by the maintainer, and the newest outside issue was answered the day it was opened. Closed issues couldn't be read (robots.txt), so the record is partial (18 of 25). Keep a Changelog with BREAKING entries and migration notes for 3.0 and 4.0 and an UPGRADING-4.0.md, but 3.3.0, which relicensed the code, has no changelog section, and 4.0.0 is dated 19 September there while only betas exist (9 of 15). Stable is 3.5.1, after two earlier majors; 4.0.0 is in beta (15). 20 + 25 + 18 + 9 + 15 = 87.)
- Schema & documentation, Composio (API + MCP) +14: Composio (API + MCP) 89 (OpenAPI 3.0 for API v3.1 with 94 paths (93 on 17 October, re-read on 1 November), and a legacy v3.0 reference, with documented 400, 401, 402, 403, 404, 409, 422 and 429 responses (25). llms.txt, llms-index.txt and llms-full.txt at docs.composio.dev (10). The seven Connect meta-tools state what each does and when, such as waiting for a user to finish OAuth, while the thousands of app tool schemas are generated from each provider and vary (14). Typed request bodies, and strict tool schemas hardened on 27 August 2026, though bare object arguments are accepted since 6 August (11). An errors reference for v3 and worked examples across the docs (14). Versioned API (v3, v3.1) and a dated changelog that flags breaking changes (15). 25 + 10 + 14 + 11 + 14 + 15 = 89.); MCP Gateway 75 (Every meta-tool declares a typed JSON Schema input with required fields, read from src/gateway/meta_mcp_tool_defs.rs, and server.json is published to the official registry. `gateway_invoke` passes backend `arguments` as an open object by design (22 of 25). llms.txt at the repository root, and Markdown docs in the tree (10). Descriptions say what each tool does and when (search first, then invoke; kill and revive say what they change for every session), and the initialize preamble names the discovery order. Backend tool descriptions come from the user's servers and aren't the gateway's (14 of 20). `gateway_list_tools` has an enum on `role`, `gateway_search` caps `limit` at 25 and `detail` is an enum, `nonce` has length bounds; `limit` on `gateway_search_tools` has no maximum (11 of 15). README, QUICKSTART, an annotated gateway-full.yaml and a troubleshooting section; errors are described in prose, with did-you-mean suggestions, and there is no error reference (8 of 15). Semver over the CLI and config file, stated in the README, and a long changelog, less for the missing 3.3.0 section and the misdated 1.0.0 and 2.0.0 entries (10 of 15). 22 + 10 + 14 + 11 + 8 + 10 = 75.)
- Agent ergonomics, Composio (API + MCP) +13: Composio (API + MCP) 90 (Composio Connect exposes seven meta-tools that search, fetch schemas, run tools in parallel and manage connections, and sessions can load only chosen toolkits (25). List endpoints page and filter, auth-config fetches go to 200 at a time, and sessions offload large responses to the sandbox (18). An error reference with codes and messages an agent can act on, and since 22 October a blocked call returns `result_type` blocked with a reason (17). Sessions filter tools by readOnlyHint, destructiveHint and idempotentHint tags, and the docs warn that non-idempotent tools aren't retried, but there are no idempotency keys (15). Official SDKs in Python and TypeScript, and a session needs only a user ID (15). 25 + 18 + 17 + 15 + 15 = 90.); MCP Gateway 77 (MCP context cost. Nine to 17 meta-tools, 11 in the default admin set, whatever the number of backends, so 15 for 11 to 30 tools, plus 10 back for Code Mode's two tools, `exposed_meta_tools` and surfaced tools (25). The project's own live run of 4 September 2026 found the meta path used 1.2 to 16.1 per cent more input tokens and one extra turn on every task, which the README states; the context saving is a schema-size saving, so less 5 (20 of 25). `gateway_search_tools` and `gateway_search` take `limit`, `gateway_search` has L0, L1 and L2 detail tiers, `gateway_list_tools` filters by server and role, and backend responses can be shaped with transform chains (17 of 20). Did-you-mean on tool names, LLM-readable output-schema failures, circuit-breaker and disabled status in `gateway_list_servers`, and rate-limited calls excluded from the kill budgets (16 of 20). Meta-tools carry readOnlyHint, destructiveHint, idempotentHint and openWorldHint; destructive meta-tools ask through elicitation, which the source calls a courtesy rather than a control; an idempotency guard exists per ADR-012 (16 of 20). One required argument for search and two for invoke; Rust only, no SDK applies, and setup takes a wizard and a config file (8 of 15). 20 + 17 + 16 + 16 + 8 = 77.)