# Merge Agent Handler vs Smithery

> Merge Agent Handler scores 69.5 (B) to Smithery's 50.7 (D) for app automation. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery
- Markdown: https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.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

Merge Agent Handler scores 69.5 (B) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories. Both do app automation.

- Merge Agent Handler: grade B, 69.5/100, rank #183 of 950. Markdown https://www.anchorterminal.com/tools/merge-agent-handler.md · JSON https://www.anchorterminal.com/api/v1/tools/merge-agent-handler.json
- Smithery: grade D, 50.7/100, rank #766 of 950. Markdown https://www.anchorterminal.com/tools/smithery.md · JSON https://www.anchorterminal.com/api/v1/tools/smithery.json
- Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md
- All 28 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md

## Which one, for what

### 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 50
- Payments & pricing, 55 against 10
- Maintenance & community, 69 against 43
- Transparency & trust, 71 against 46

Also in its favour:
- Free to start without a card

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

### Smithery (D)

Good for: A developer who wants many MCP servers behind one credential and one endpoint, with per-user connections and short-lived scoped tokens.

Watch for: No terms of service are linked from the site, the docs or the footer. The privacy notice of 20 June 2025 is the only legal document found


## Score by category

| Category | Weight | Merge Agent Handler | Smithery | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 59 | 60 | Smithery +1 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 76 | Merge Agent Handler +4 |
| Agent ergonomics | 13% (16.2 this run) | 68 | 65 | Merge Agent Handler +3 |
| Security & auth | 14% (17.5 this run) | 83 | 50 | Merge Agent Handler +33 |
| Payments & pricing | 10% (12.5 this run) | 55 | 10 | Merge Agent Handler +45 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 69 | 43 | Merge Agent Handler +26 |
| Transparency & trust | 7% (8.8 this run) | 71 | 46 | Merge Agent Handler +25 |
| Negative events | ≤15 | 0 | -2 | |
| **Total** | | **69.5 · B** | **50.7 · D** | |

## Facts side by side

| Fact | Merge Agent Handler | Smithery |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Merge API, Inc. | Smithery (Arcade.dev) |
| Hosted endpoint | `https://ah-api.merge.dev/mcp` | `https://api.smithery.ai` |
| Transports | Streamable HTTP, HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | 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 | Proprietary hosted service, with no terms of service found. The CLI (`smithery`) is AGPL-3.0, the TypeScript client (`@smithery/api`) is Apache-2.0 and the credential layer agent.pw is MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-07-20 |
| Terms last updated | 2026-09-09 | no document linked |
| Privacy policy last updated | 2026-08-20 | 2025-06-20 |
| Customer content may train models | not found in the text |  |
| Terms restrict automated access | not found in the text |  |
| Terms restrict benchmarking | yes |  |
| Terms or service can change without notice | not found in the text |  |
| Arbitration or class-action waiver | not found in the text |  |
| Popularity | 681 PyPI/wk | 840 stars, 2.7k npm/wk |

## Verdicts

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

**Smithery.** Service tokens can be limited by namespace, resource, operation and connection metadata, with a lifetime of at most 24 hours. No terms of service, rate limits or SLA were found, the pricing page could not be read, and the newest client release is from 20 July 2026.

## Before you call either

### 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_<connector>` 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`

### Smithery

1. Keep the API key on the backend and hand an agent a service token limited to `connections` with `read` and `execute` and a `metadata` match
2. Create connections with `PUT /connect/{namespace}/{connectionId}`, which is an upsert, and check `status.state` before calling a tool
3. On `auth_required` or `input_required`, send the person to `setupUrl`, then retry with the same `connectionId`
4. Tool names on the namespace MCP endpoint are prefixed with the connection ID, such as `user-123-github.search_repositories`
5. Do not rely on `smithery skill` commands. Version 1.1.1 of the CLI removed them

## Questions

### Which is better for AI agents, Merge Agent Handler or Smithery?

Merge Agent Handler scores 69.5 (B) on agent readiness against Smithery's 50.7 (D), and leads in 6 of 7 scored categories.

### Do Merge Agent Handler and Smithery need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Merge Agent Handler and Smithery without installing anything?

Yes. Merge Agent Handler has a hosted endpoint at https://ah-api.merge.dev/mcp and Smithery at https://api.smithery.ai.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.json, and with the fewest tokens: https://www.anchorterminal.com/compare/merge-agent-handler-vs-smithery.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "merge-agent-handler", "b": "smithery"}`. From a terminal: `anchor compare merge-agent-handler smithery`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/merge-agent-handler.json and https://www.anchorterminal.com/api/v1/tools/smithery.json

## Other comparisons with Merge Agent Handler or Smithery

- [Composio (API + MCP) vs Merge Agent Handler](https://www.anchorterminal.com/compare/composio-rube-vs-merge-agent-handler.md)
- [Composio (API + MCP) vs Smithery](https://www.anchorterminal.com/compare/composio-rube-vs-smithery.md)
- [Merge Agent Handler vs One](https://www.anchorterminal.com/compare/merge-agent-handler-vs-one.md)
- [Merge Agent Handler vs StackOne](https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.md)
- [Merge Agent Handler vs Unified.to MCP Server](https://www.anchorterminal.com/compare/merge-agent-handler-vs-unified-to-mcp.md)
- [Merge Agent Handler vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/merge-agent-handler-vs-zapier-mcp.md)
- [One vs Smithery](https://www.anchorterminal.com/compare/one-vs-smithery.md)
- [Smithery vs StackOne](https://www.anchorterminal.com/compare/smithery-vs-stackone.md)
- [Smithery vs Unified.to MCP Server](https://www.anchorterminal.com/compare/smithery-vs-unified-to-mcp.md)
- [Smithery vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/smithery-vs-zapier-mcp.md)
- [letme vs Merge Agent Handler](https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.md)
- [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md)