Head to head · App automation · October 2026 research run
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.
Which one, for what
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
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 this run | Composio (API + MCP) | Merge Agent Handler | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 59 | Composio (API + MCP) +11 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 80 | Composio (API + MCP) +9 |
| Agent ergonomics | 13%16.2 | 90 | 68 | Composio (API + MCP) +22 |
| Security & auth | 14%17.5 | 70 | 83 | Merge Agent Handler +13 |
| Payments & pricing | 10%12.5 | 40 | 55 | Merge Agent Handler +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 93 | 69 | Composio (API + MCP) +24 |
| Transparency & trust | 7%8.8 | 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)
- Create one session per end user with a stable database ID, never an email or
default - Pass the Connect Link from COMPOSIO_MANAGE_CONNECTIONS to the user and call COMPOSIO_WAIT_FOR_CONNECTIONS rather than asking for credentials
- Filter the session to
readOnlyHinttools when the task only reads - Don't retry a timed-out send or create call blind, check the app first, since the SDKs won't retry it either
- Replace any rube.app/mcp entry with connect.composio.dev/mcp or a session MCP URL
Merge Agent Handler
- Call
search_toolswith a plain-language intent beforetools/list. A Tool Pack can hold hundreds of tools and Slack alone lists 50 - Add
?connectors=slackto the MCP URL to limit a connection to named connectors, and?paginated=trueonly if the client followsnextCursor - Carry a user-scoped key with
runtime:allonly. The production key reaches every Registered User and the management endpoints - On
reauth_requiredreaddata.reauth_reason, then callauthenticate_<connector>by name. Intent search doesn't return the authenticate tools - Pin
MCP-Protocol-Versionto2025-03-26when context is tight. Later revisions repeat object results instructuredContent
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.
Other comparisons with Composio (API + MCP) or Merge Agent Handler
Machine-readable
- This page as Markdown
/compare/composio-rube-vs-merge-agent-handler.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/composio-rube.json·/api/v1/tools/merge-agent-handler.json - From a terminal
anchor compare composio-rube merge-agent-handler(the CLI) - Over MCP
compare_tools {"a": "composio-rube", "b": "merge-agent-handler"}at/mcp, no key