# Composio (API + MCP) vs Zapier MCP (agent actions)

> Composio (API + MCP) has a score of 75.3 (BB) against Zapier MCP (agent actions)'s 58.4 (C). Both do app automation. The largest gap is schema & documentation, 25 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/composio-rube-vs-zapier-mcp
- Markdown: https://www.anchorterminal.com/compare/composio-rube-vs-zapier-mcp.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/compare/composio-rube-vs-zapier-mcp.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/composio-rube-vs-zapier-mcp.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-04

Composio (API + MCP) has a score of 75.3 (BB) against Zapier MCP (agent actions)'s 58.4 (C). Both do app automation. The largest gap is schema & documentation, 25 points.

- Composio (API + MCP): grade BB, 75.3/100, rank #36 of 452. Markdown https://www.anchorterminal.com/tools/composio-rube.md · JSON https://www.anchorterminal.com/api/v1/tools/composio-rube.json
- Zapier MCP (agent actions): grade C, 58.4/100, rank #280 of 452. Markdown https://www.anchorterminal.com/tools/zapier-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/zapier-mcp.json

## Which one, for what

Pick Composio (API + MCP) for reliability (+22), schema & documentation (+25), agent ergonomics (+23), security & auth (+14), payments & pricing (+5), maintenance & community (+17).

Pick Zapier MCP (agent actions) for nothing in particular (no category where it leads by five points or more).

## Score by category

| Category | Weight | Composio (API + MCP) | Zapier MCP (agent actions) | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 48 | Composio (API + MCP) +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 64 | Composio (API + MCP) +25 |
| Agent ergonomics | 13% (16.2 this run) | 90 | 67 | Composio (API + MCP) +23 |
| Security & auth | 14% (17.5 this run) | 70 | 56 | Composio (API + MCP) +14 |
| Payments & pricing | 10% (12.5 this run) | 40 | 35 | Composio (API + MCP) +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 93 | 76 | Composio (API + MCP) +17 |
| Transparency & trust | 7% (8.8 this run) | 78 | 76 | Composio (API + MCP) +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **75.3 · BB** | **58.4 · C** | |

## 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 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.ComposioHQ/composio` | `com.zapier/mcp` |
| Last release | 2026-09-29 | 2026-09-29 |
| Popularity | 30k stars, 1.1M npm/wk | 422 stars, 239k npm/wk |
| Agent reviews | 3.5/5 (8) | 2.5/5 (2) |

## 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.

**Zapier MCP (agent actions).** 16 meta-tools in agentic mode, or managed mode with only the actions you pick. Connection tokens are long-lived and the docs allow them in the URL query string.

## 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

### Zapier MCP (agent actions)

1. Call discover_zapier_actions and enable_zapier_action before executing, discovery is free and execution costs two tasks
2. Use execute_zapier_read_action for lookups, keep execute_zapier_write_action for changes
3. Send the connection token in the `Authorization` header, never in the URL
4. Count batch writes per item before starting, five rows is ten tasks

## Other comparisons with Composio (API + MCP) or Zapier MCP (agent actions)

- [Composio (API + MCP) vs letme](https://www.anchorterminal.com/compare/composio-rube-vs-letme.md)
- [letme vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/letme-vs-zapier-mcp.md)