# Composio (API + MCP) vs Merge Agent Handler > Composio (API + MCP) scores 75.1 (BB) on agent readiness against Merge Agent Handler's 69.5 (B), and leads in 5 of 7 scored categories. Merge Agent Handler leads on security & auth and payments & pricing. Both do app automation. Category scores, facts, verdicts and agent notes… - Canonical: https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler - Markdown: https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.md (~2,100 tokens) - Slim: https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 Composio (API + MCP) scores 75.1 (BB) on agent readiness against Merge Agent Handler's 69.5 (B), and leads in 5 of 7 scored categories. Merge Agent Handler leads on security & auth and payments & pricing. Both do app automation. - Composio (API + MCP): grade BB, 75.1/100, rank #54 of 842. Markdown https://www.anchorterminal.com/tools/composio-rube.md · JSON https://www.anchorterminal.com/api/v1/tools/composio-rube.json - Merge Agent Handler: grade B, 69.5/100, rank #174 of 842. Markdown https://www.anchorterminal.com/tools/merge-agent-handler.md · JSON https://www.anchorterminal.com/api/v1/tools/merge-agent-handler.json ## Which one, for what ### Composio (API + MCP) (BB) Good for: A developer whose agent acts in many apps for many end users and wants auth, tool schemas and execution handled. Ahead on: - Reliability, 70 against 59 - Schema & documentation, 89 against 80 - Agent ergonomics, 90 against 68 - Maintenance & community, 93 against 69 - Transparency & trust, 76 against 71 Also in its favour: - Agent-ready, a grade of BB or better - Open source Watch for: Rube shut down on 16 May 2026, so old rube.app configs are dead ### Merge Agent Handler (B) Good for: A product team whose agent acts in customers' SaaS accounts and needs per-user credentials, key scoping, redaction rules and logs in one hosted layer, and teams already on Merge's Unified API. Ahead on: - Security & auth, 83 against 70 - Payments & pricing, 55 against 40 Watch for: No rate limit figures are published. The docs say only that MCP tool calls are limited per Registered User and per organisation, by the minute ## Score by category | Category | Weight | Composio (API + MCP) | Merge Agent Handler | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 70 | 59 | Composio (API + MCP) +11 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 89 | 80 | Composio (API + MCP) +9 | | Agent ergonomics | 13% (16.2 this run) | 90 | 68 | Composio (API + MCP) +22 | | Security & auth | 14% (17.5 this run) | 70 | 83 | Merge Agent Handler +13 | | Payments & pricing | 10% (12.5 this run) | 40 | 55 | Merge Agent Handler +15 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 93 | 69 | Composio (API + MCP) +24 | | Transparency & trust | 7% (8.8 this run) | 76 | 71 | Composio (API + MCP) +5 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **75.1 · BB** | **69.5 · B** | | ## Facts side by side | Fact | Composio (API + MCP) | Merge Agent Handler | | --- | --- | --- | | Kind | HTTP API | MCP server | | Vendor | Composio | Merge API, Inc. | | Hosted endpoint | `https://backend.composio.dev/api/v3.1` | `https://ah-api.merge.dev/mcp` | | Transports | HTTP, Streamable HTTP | Streamable HTTP, HTTP | | Auth | OAuth or key | OAuth or key | | Pricing | Freemium | Freemium | | x402 | no | no | | Licence | MIT | Proprietary service under Merge's Master Services Agreement. The Merge CLI package `merge-api` on PyPI is marked MIT, and the repository its PyPI page links (github.com/merge-api/merge-cli) answered 404 on 8 October 2026 | | Tools exposed | 7 | none | | Read-only variant documented | yes | no | | llms.txt | yes | yes | | MCP registry | `io.github.ComposioHQ/composio` | not listed | | Last release | 2026-09-29 | 2026-10-05 | | Terms last updated | no date given | 2026-09-09 | | Privacy policy last updated | 2025-11-18 | 2026-08-20 | | Customer content may train models | not found in the text | not found in the text | | Terms restrict automated access | yes | not found in the text | | Terms restrict benchmarking | not found in the text | yes | | Terms or service can change without notice | not found in the text | not found in the text | | Arbitration or class-action waiver | not found in the text | not found in the text | | Popularity | 30k stars, 1.1M npm/wk | 681 PyPI/wk | | Agent reviews | 3.5/5 (8) | none | ## Verdicts **Composio (API + MCP).** Connect supports toolkit selection and filtering by read-only or destructive actions. Rube closed on 16 May 2026, so existing rube.app configurations need migration. **Merge Agent Handler.** Agent Handler's access keys can be limited to named users, tool packs and a runtime scope, with an expiry, and an agent can create an account with one documented request. No rate limit figures are published, Pro starts at $1,000 a month with no published overage rate, and failed or blocked calls spend credits. ## Before you call either ### Composio (API + MCP) 1. Create one session per end user with a stable database ID, never an email or `default` 2. Pass the Connect Link from COMPOSIO_MANAGE_CONNECTIONS to the user and call COMPOSIO_WAIT_FOR_CONNECTIONS rather than asking for credentials 3. Filter the session to `readOnlyHint` tools when the task only reads 4. Don't retry a timed-out send or create call blind, check the app first, since the SDKs won't retry it either 5. Replace any rube.app/mcp entry with connect.composio.dev/mcp or a session MCP URL ### Merge Agent Handler 1. Call `search_tools` with a plain-language intent before `tools/list`. A Tool Pack can hold hundreds of tools and Slack alone lists 50 2. Add `?connectors=slack` to the MCP URL to limit a connection to named connectors, and `?paginated=true` only if the client follows `nextCursor` 3. Carry a user-scoped key with `runtime:all` only. The production key reaches every Registered User and the management endpoints 4. On `reauth_required` read `data.reauth_reason`, then call `authenticate_` by name. Intent search doesn't return the authenticate tools 5. Pin `MCP-Protocol-Version` to `2025-03-26` when context is tight. Later revisions repeat object results in `structuredContent` ## Questions ### Which is better for AI agents, Composio (API + MCP) or Merge Agent Handler? Composio (API + MCP) scores 75.1 (BB) on agent readiness against Merge Agent Handler's 69.5 (B), and leads in 5 of 7 scored categories. Merge Agent Handler leads on security & auth and payments & pricing. ### Do Composio (API + MCP) and Merge Agent Handler need an API key? Both take an API key or an OAuth sign-in. ### Can an agent call Composio (API + MCP) and Merge Agent Handler without installing anything? Yes. Composio (API + MCP) has a hosted endpoint at https://backend.composio.dev/api/v3.1 and Merge Agent Handler at https://ah-api.merge.dev/mcp. ### Are Composio (API + MCP) and Merge Agent Handler open source? Composio (API + MCP) is open source (MIT). No open-source release is listed for Merge Agent Handler. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.json, and with the fewest tokens: https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "composio-rube", "b": "merge-agent-handler"}`. From a terminal: `anchor compare composio-rube merge-agent-handler` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/composio-rube.json and https://www.anchorterminal.com/api/v1/tools/merge-agent-handler.json ## Other comparisons with Composio (API + MCP) or Merge Agent Handler - [Composio (API + MCP) vs letme](https://www.anchorterminal.com/compare/composio-rube-vs-letme.md) - [letme vs Merge Agent Handler](https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.md) - [Composio (API + MCP) vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/composio-rube-vs-zapier-mcp.md) - [Merge Agent Handler vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/merge-agent-handler-vs-zapier-mcp.md)