Head to head · App automation · October 2026 research run
Merge Agent Handler vs One
Merge Agent Handler scores 69.5 (B) on agent readiness against One's 66.6 (B), and leads in 4 of 7 scored categories. One leads on reliability, agent ergonomics and maintenance & community. Both do app automation.
Best agent tool access platforms · All 28 tool access comparisons
Which one, for what
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 69
- Payments & pricing, 55 against 30
- Transparency & trust, 71 against 63
Also in its favour
- Free to start without a card
- No incidents deducted, where One loses 3 points for them
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
One B
Good for A person or small team that wants one MCP entry with a small tool footprint across many SaaS accounts, with access set per connection and a free plan.
Ahead on
- Reliability, 82 against 59
- Agent ergonomics, 73 against 68
- Maintenance & community, 86 against 69
Also in its favour
- Runs on your own machine
Watch for
The remote server's tools changed from four to three by 30 September 2026, and the site's changelog, last dated 13 July 2026, has no entry for it
Score by category
| Category | Weight this run | Merge Agent Handler | One | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 59 | 82 | One +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 80 | 77 | Merge Agent Handler +3 |
| Agent ergonomics | 13%16.2 | 68 | 73 | One +5 |
| Security & auth | 14%17.5 | 83 | 69 | Merge Agent Handler +14 |
| Payments & pricing | 10%12.5 | 55 | 30 | Merge Agent Handler +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 69 | 86 | One +17 |
| Transparency & trust | 7%8.8 | 71 | 63 | Merge Agent Handler +8 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 69.5 · B | 66.6 · B |
Facts side by side
| Fact | Merge Agent Handler | One |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Merge API, Inc. | One Systems, Inc. |
| Hosted endpoint | https://ah-api.merge.dev/mcp | https://mcp.withone.ai/mcp |
| Transports | Streamable HTTP, HTTP | Streamable HTTP, stdio |
| 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 under One's Terms of Service. The local MCP server package @withone/mcp is MIT. The CLI package @withone/cli has no licence field or licence file. The knowledge base is under the One Knowledge Commons Licence v1.0, which is not an OSI licence |
| Tools exposed | none | 3 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | ai.withone/mcp |
| Last release | 2026-10-05 | 2026-10-06 |
| Terms last updated | 2026-09-09 | 2026-03-06 |
| Privacy policy last updated | 2026-08-20 | 2026-07-22 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | 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 | 681 PyPI/wk | 11 stars, 681 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.
One
One's remote MCP server has three tools, OAuth 2.1 sign-in with PKCE and a consent screen that sets read only, read and write, full or per-action access for each connection. A person must sign in through a browser, the SOC 2 audit is unfinished, and the site's changelog stops at 13 July 2026.
Before you call either
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
One
- Call
list_one_integrationsfirst and read each connection'saccessfield. When the policy isactions, run those ids directly without callingfind_one_actions - Send every operation a task needs in one
find_one_actionscall, up to 10requests, each a platform and a short intent with no IDs, names or message text - When a document comes back as a digest, call
find_one_actionsagain withloadand asectionname. Don't guess parameters the digest left out - After a timeout on
execute_one_action, check whether the write took effect before sending it again. No idempotency key is documented - A 403 for a call outside the grant won't succeed on retry. Ask the user to widen the grant in the dashboard or reconnect
Questions
Which is better for AI agents, Merge Agent Handler or One?
Merge Agent Handler scores 69.5 (B) on agent readiness against One's 66.6 (B), and leads in 4 of 7 scored categories. One leads on reliability, agent ergonomics and maintenance & community.
Do Merge Agent Handler and One need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Merge Agent Handler and One without installing anything?
Yes. Merge Agent Handler has a hosted endpoint at https://ah-api.merge.dev/mcp and One at https://mcp.withone.ai/mcp.
Other comparisons with Merge Agent Handler or One
- Composio (API + MCP) vs Merge Agent Handler
- Composio (API + MCP) vs One
- Merge Agent Handler vs Smithery
- Merge Agent Handler vs StackOne
- Merge Agent Handler vs Unified.to MCP Server
- Merge Agent Handler vs Zapier MCP (agent actions)
- One vs Smithery
- One vs StackOne
- One vs Unified.to MCP Server
- One vs Zapier MCP (agent actions)
- letme vs Merge Agent Handler
- letme vs One
Machine-readable
- This page as Markdown
/compare/merge-agent-handler-vs-one.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/merge-agent-handler.json·/api/v1/tools/one.json - From a terminal
anchor compare merge-agent-handler one(the CLI) - Over MCP
compare_tools {"a": "merge-agent-handler", "b": "one"}at/mcp, no key