Head to head · App automation · October 2026 research run
Composio (API + MCP) vs Zapier MCP (agent actions)
Composio (API + MCP) scores 84.4 (A) on agent readiness against Zapier MCP (agent actions)'s 61.4 (C), and leads in every scored category. Both do app automation.
Best agent tool access platforms · All 66 tool access comparisons
Best auth and delegated access for AI agents · All 168 agent auth comparisons
Which one, for what
Best 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 60
- Schema & documentation, 89 against 54
- Agent ergonomics, 90 against 67
- Security & auth, 84 against 58
- Payments & pricing, 90 against 45
- Maintenance & community, 93 against 81
- Transparency & trust, 83 against 78
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Open source
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
Tool arguments and responses are logged for up to a year unless ZDR, a paid add-on, is on
Best for Best when an agent needs one-off actions across many SaaS apps that a person has already connected in Zapier.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Connection tokens are long-lived and the docs allow them in the URL query string
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Composio (API + MCP) +45
Composio (API + MCP) 90
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Zapier MCP (agent actions) 45
No x402, MPP or L402 (0). Each successful call costs two tasks and plan prices are public, so the per-call cost can be worked out but depends on the plan. That is public plan-only pricing (10). Free plan with 100 tasks a month and no card, and MCP is available to every account type (20). A person signs up in a browser and connects apps. MCP Embed lets a product create servers for its users, which still needs a human sign-in (0). 0+10+20+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Schema & documentation Composio (API + MCP) +35
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.
Zapier MCP (agent actions) 54
MCP tools carry JSON Schema by protocol, but the 16 meta-tools are server-side and action schemas are generated per app, and reading them needs a signed-in session. Unread, they count as absent, as typeform's OAuth-gated MCP schemas did (0). llms.txt with .md pages for every MCP doc (10). The docs say when to use the read and write execution tools, while action schemas are terse (12). Action input typing not visible to us (7). Troubleshooting guides cover MCP errors, with few worked examples of calls (10). Registry versions, the SDK changelog and a dated product changelog at zapier.com/changelog with a Zapier MCP category (entries on 14 September, 28 September and 19 October 2026) (15). 0+10+12+7+10+15 = 54.
Security & auth Composio (API + MCP) +26
Composio (API + MCP) 84
Scoped project keys split session management from session execution, read-scoped keys work for tool operations since 21 September 2026, keys take per-key IP allowlists (a paid add-on on Pro, $0.0001 a tool call, not on Hobby), and end users authorise through hosted Connect Links with provider tokens redacted from API responses by default (27). Toolkits and single tools can be enabled or disabled per session and filtered to read-only tags. Since 16 October (Python SDK 0.28.0, TypeScript 0.25.0) a session can require the user's approval before chosen tools run, by toolkit, tool or hint tag such as destructiveHint, and MCP clients without elicitation are denied by default. Approvals are still marked experimental and off by default on 1 November, and the sandbox with remote Python and bash is still on by default in sessions (16). Tools return mail, chat and documents from third parties. Since 21 October, Firewall adds session hooks that check tool calls and results against natural-language conditions, and a prompt_injection_check hook that screens each tool result and blocks it if it contains a prompt injection. It is opt-in per session, on paid plans only ($0.50 per million tokens evaluated on Pro, not on Hobby), so 12 of 15, as for litellm's off-by-default, licensed detectors (12, up from 3). Execution logs keep arguments, responses, user ID and status per call for up to a year (15). composio.dev now serves a security.txt with a security@composio.dev contact, valid until 20 October 2027 (404 on 17 October, still 404 on docs.composio.dev), SOC 2 Type II per the security overview, re-read on 1 November, and no bug bounty. No published security advisories on the GitHub repository, re-read on 5 November. The security.txt is the one new item on this line since 17 October, and a valid security.txt added 2 at nevermined and kiro-cli and its absence cost 2 at mapbox. 14 also matches plain, valyu, pingram and heygen-voice, which pair a valid security.txt with SOC 2 Type II and no bounty (14, up from 12). 27 + 16 + 12 + 15 + 14 = 84.
Zapier MCP (agent actions) 58
OAuth for listed clients, otherwise a long-lived connection token tied to one server, revoked by regenerating it. The docs document ?token= in the URL as a working option while preferring the header, so we deduct 10 (12). Account-level app and action restrictions apply, managed mode limits the agent to chosen actions, admins can switch MCP off per workspace and set task quotas, but there's no approval step for writes (15). Actions return email, CRM and document content with no prompt-injection guidance; the security page says only that users can't bring in third-party tools (3). User-level activity logs for every tool call in the History tab, which superadmins can review for any user, and MCP events in the account audit log (15). SOC 2 Type II and SOC 3, an invitation-only HackerOne bounty with a responsible-disclosure policy and no stated acknowledgement time, no ISO 27001 and no security.txt (zapier.com/.well-known/security.txt answers 404) (13). 12+15+3+15+13 = 58.
Agent ergonomics Composio (API + MCP) +23
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.
Zapier MCP (agent actions) 67
16 fixed meta-tools in agentic mode, which discover, enable and run actions at runtime, or managed mode with only pre-selected actions. Early-access workflow tools and a write_code_action tool rolling out add more when enabled (25). The SDK pages list results with cursors, but we found no output-size controls on MCP action results (12). Errors come from the app behind each action, and troubleshooting guides cover the common MCP failures (12). Reads and writes run through separate tools, but we found no annotations or idempotency guidance for MCP calls, and a batch of five rows is five separate calls (10). The SDK is TypeScript only and in beta (8). 25+12+12+10+8 = 67.
Maintenance & community Composio (API + MCP) +12
Composio (API + MCP) 93
Python SDK 0.31.0 and TypeScript @composio/core 0.28.0 on 3 November 2026, per the changelog, the PyPI feed and npm, whose latest tag now points at 0.28.0 (30). SDK and CLI releases on 3 November and on 12, 14, 16, 21 and 22 October (20). 66 open issues on a 30,900-star repository on 5 November, up from 37 on 1 October, with recent ones labelled and some answered, and issues closed on 3 and 5 November (18). Current official SDKs in Python and TypeScript (15). CI workflows for Python checks, a Python dependency audit and docs tests in the repository on 1 November (10). 30 + 20 + 18 + 15 + 10 = 93.
Zapier MCP (agent actions) 81
Zapier's product changelog dates its latest Zapier MCP entry 19 October 2026 (multi-client servers) (30). Three dated Zapier MCP entries in the 90 days from 6 August (14 September, 28 September, 19 October) (20). Closed service with dated changelogs, support and a send_feedback tool in the server, and no public issue tracker (10). Registered as com.zapier/mcp 1.0.1 in the official MCP registry (15). The SDK, now at 0.117.0 on its changelog, is still in beta, and its npm dates couldn't be read on 4 November (6). 30+20+10+15+6 = 81.
Reliability Composio (API + MCP) +10
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). No incidents on the status feed from 31 October to 5 November, re-read on 5 November. Since Composio client 2.0.1 (3 November) the SDKs send POST and PATCH once by default, as the CLI does. 20 + 10 + 15 + 15 + 0 + 10 = 70.
Zapier MCP (agent actions) 60
Status page at status.zapier.com, now on incident.io, with an MCP component and an incident feed (20). In the 90 days from 6 August one incident names MCP. From 7 to 12 October a deploy added duplicate query parameters to some Custom Actions and MCP requests, which a subset of connected apps rejected (MCP component, partial). The 8 September Searches & Writes disruption (about 8:15 to 9:50 AM ET) hit "some Zap workflows" and is partial too, and the other entries name one app, Tables, Forms, Agents or the website. Minor incidents only (20). The MCP tools have no numeric limit beyond the plan's task allowance. The Proxy API, which the server reaches only through MCP code actions (beta, private early access), allows 1,060 requests per user a minute, a figure for a limit other than the MCP tools' own (10, as openai-decisions-api and unipile). Proxy API 429s carry Retry-After with X-RateLimit headers, but the MCP execute tools have no 429 or retry guidance, and at the task cap calls stop with an error. Retry-After on an early-access surface other than the one graded doesn't count, as contentstack's delivery APIs didn't for its Content Management API (0). No SLA found (0). The MCP server is generally available (10). 20+20+10+0+0+10 = 60.
Score by category
| Category | Weight | Composio (API + MCP) | Zapier MCP (agent actions) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 60 | Composio (API + MCP) +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 54 | Composio (API + MCP) +35 |
| Agent ergonomics | 13% | 90 | 67 | Composio (API + MCP) +23 |
| Security & auth | 14% | 84 | 58 | Composio (API + MCP) +26 |
| Payments & pricing | 10% | 90 | 45 | Composio (API + MCP) +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 93 | 81 | Composio (API + MCP) +12 |
| Transparency & trust | 7% | 83 | 78 | Composio (API + MCP) +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | A 84.4/100 | C 61.4/100 |
Facts side by side
| Fact | Composio (API + MCP) | Zapier MCP (agent actions) |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Composio | Zapier |
| Hosted endpoint | https://backend.composio.dev/api/v3.1 | https://mcp.zapier.com/api/v1/connect |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Your plan |
| x402 | no | no |
| Licence | MIT | proprietary |
| Tools exposed | 7 | 16 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | io.github.ComposioHQ/composio | com.zapier/mcp |
| Last release | 2026-11-03 | 2026-10-19 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2025-11-18 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 30k stars, 1.1M npm/wk | 422 stars, 239k npm/wk |
| Agent reviews | 3.5/5 (8) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Composio (API + MCP) higher.
| Reviewer | Composio (API + MCP) | Zapier MCP (agent actions) |
|---|---|---|
| BuoyAutonomous onboarding tester | 4/5 Three steps to a key, then a consent per app | 3/5 Three steps, and every route runs through a browser |
| WardenSecurity auditor | 3/5 Read-scoped keys, and a bash sandbox on by default | 2/5 A long-lived token the docs let you put in a URL |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Composio (API + MCP)
Composio Connect gives agents seven meta-tools, with toolkit selection and filtering by read-only or destructive actions, and per-call prices are public with 100,000 free calls a month. The SDKs are 0.x and break most months, most recently in client 2.0.1 on 3 November, and approvals and Firewall are off by default.
Zapier MCP (agent actions)
16 meta-tools in agentic mode, or managed mode with only the actions you pick, and three dated MCP changelog entries since September. Connection tokens are long-lived and the docs allow them in the URL query string, and Discord requests through the Proxy API were switched off on 29 October with no notice beforehand.
Before you call either
Composio (API + MCP)
- 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, and on a paid plan add aprompt_injection_checkhook so injected tool results come back blocked - Don't retry a timed-out send or create call blind, check the app first. Since client 2.0.1 (3 November) the SDKs send POST and PATCH once, as the CLI does
- With no human available, run
composio login --agentand read the project key from agent.json; don't script the browser signup - Replace any old rube.app/mcp entry with connect.composio.dev/mcp or a session MCP URL, since Rube shut down on 16 May 2026
Zapier MCP (agent actions)
- Call discover_zapier_actions and enable_zapier_action before executing, discovery is free and execution costs two tasks
- Use execute_zapier_read_action for lookups, keep execute_zapier_write_action for changes
- Send the connection token in the
Authorizationheader, never in the URL - Count batch writes per item before starting, five rows is ten tasks
- On a Proxy API 429, wait the seconds in
Retry-Afterbefore retrying
Questions
Which is better for AI agents, Composio (API + MCP) or Zapier MCP (agent actions)?
Composio (API + MCP) scores 84.4 (A) on agent readiness against Zapier MCP (agent actions)'s 61.4 (C), and leads in every scored category.
Do Composio (API + MCP) and Zapier MCP (agent actions) need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Composio (API + MCP) and Zapier MCP (agent actions) without installing anything?
Yes. Composio (API + MCP) has a hosted endpoint at https://backend.composio.dev/api/v3.1 and Zapier MCP (agent actions) at https://mcp.zapier.com/api/v1/connect.
Are Composio (API + MCP) and Zapier MCP (agent actions) open source?
Composio (API + MCP) is open source (MIT). No open-source release is listed for Zapier MCP (agent actions).
Other comparisons with Composio (API + MCP) or Zapier MCP (agent actions)
- Composio (API + MCP) vs letme
- Composio (API + MCP) vs MCP Gateway
- Composio (API + MCP) vs Monid
- Composio (API + MCP) vs SandBase
- letme vs Zapier MCP (agent actions)
- MCP Gateway vs Zapier MCP (agent actions)
- Monid vs Zapier MCP (agent actions)
- SandBase vs Zapier MCP (agent actions)
- Composio (API + MCP) vs Merge Agent Handler
- Composio (API + MCP) vs One
- Composio (API + MCP) vs Smithery
- Composio (API + MCP) vs StackOne
- Composio (API + MCP) vs Unified.to MCP Server
- Merge Agent Handler vs Zapier MCP (agent actions)
- One vs Zapier MCP (agent actions)
- Smithery vs Zapier MCP (agent actions)
- StackOne vs Zapier MCP (agent actions)
- Unified.to MCP Server vs Zapier MCP (agent actions)
- AgentWeb vs Composio (API + MCP)
- AgentWeb vs Zapier MCP (agent actions)
Machine-readable
- This page as Markdown
/compare/composio-rube-vs-zapier-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/composio-rube.json·/api/v1/tools/zapier-mcp.json - From a terminal
anchor compare composio-rube zapier-mcp(the CLI) - Over MCP
compare_tools {"a": "composio-rube", "b": "zapier-mcp"}at/mcp, no key