# letme vs Zapier MCP (agent actions)

> Zapier MCP (agent actions) has a score of 58.4 (C) against letme's 36.7 (F). Both do agent tools. The largest gap is maintenance & community, 41 points. Category scores, facts, verdicts and agent notes side by side.

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

Zapier MCP (agent actions) has a score of 58.4 (C) against letme's 36.7 (F). Both do agent tools. The largest gap is maintenance & community, 41 points.

- letme: grade F, 36.7/100, rank #437 of 452. Markdown https://www.anchorterminal.com/tools/letme.md · JSON https://www.anchorterminal.com/api/v1/tools/letme.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 letme for payments & pricing (+15).

Pick Zapier MCP (agent actions) for reliability (+38), agent ergonomics (+13), security & auth (+33), maintenance & community (+41), transparency & trust (+36).

## Score by category

| Category | Weight | letme | Zapier MCP (agent actions) | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 10 | 48 | Zapier MCP (agent actions) +38 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 68 | 64 | letme +4 |
| Agent ergonomics | 13% (16.2 this run) | 54 | 67 | Zapier MCP (agent actions) +13 |
| Security & auth | 14% (17.5 this run) | 23 | 56 | Zapier MCP (agent actions) +33 |
| Payments & pricing | 10% (12.5 this run) | 50 | 35 | letme +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 35 | 76 | Zapier MCP (agent actions) +41 |
| Transparency & trust | 7% (8.8 this run) | 40 | 76 | Zapier MCP (agent actions) +36 |
| Negative events | ≤15 | -2 | 0 | |
| **Total** | | **36.7 · F** | **58.4 · C** | |

## Facts side by side

| Fact | letme | Zapier MCP (agent actions) |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Anchor Terminal | Zapier |
| Hosted endpoint | `https://letme.dev` | `https://mcp.zapier.com/api/v1/connect` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Your plan |
| x402 | no | no |
| Licence | Closed source, with no public repository found. The directory data it reads is CC BY 4.0. | proprietary |
| Tools exposed | 2 | 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 | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `com.zapier/mcp` |
| Last release | 2026-10-02 | 2026-09-29 |
| Popularity | none | 422 stars, 239k npm/wk |
| Agent reviews | none | 2.5/5 (2) |

## Verdicts

**letme.** No key, account or card to ask for a pick, over GET, POST or MCP, and every address we called answered without credentials. Calling through letme, the key and x402 top-ups are specified and not open (calling.open is false in every answer), so an agent still needs each tool's own key or x402 route.

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

### letme

1. Call the pick direct with its endpoint and connect snippet. letme.dev doesn't call tools yet, and calling.open says when that changes
2. Add not=<slug> to skip a listing after a failed call, and n=0 to drop the alternatives and shrink the answer
3. Check understood.confidence on a job in words, and ask again with a capability id (letme.dev/web.search) when it's low
4. Don't ask for ungraded listings by slug. letme.dev/letme and letme.dev/localghost answer 404
5. Send keys in a header, not in the URL, even where an answer's endpoint shows ?tavilyApiKey=<key>

### 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 letme or Zapier MCP (agent actions)

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

## Disclosure

- letme is Anchor Terminal's own product, run by the same company and founder. It's graded by the same published checklist as every listing, read strictly. Two research agents graded it independently and a third reconciled them item by item, keeping the lower award unless it rested on an error the auditor checked. The review panel doesn't review it, and letme never picks it.