Head to head · App automation · October 2026 research run
Merge Agent Handler vs StackOne
Merge Agent Handler and StackOne score within a point of each other on agent readiness, 69.5 (B) and 69.1 (B). StackOne 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 38
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
StackOne B
Good for A company that wants one governed MCP endpoint for staff agents across business systems, and product teams embedding per-customer connections with HR, recruiting and CRM coverage.
Ahead on
- Reliability, 80 against 59
- Agent ergonomics, 75 against 68
- Maintenance & community, 84 against 69
Watch for
Session token URLs (https://api.stackone.com/mcp?token=...) put the credential in the query string, cover one linked account and expire after one year by default
Score by category
| Category | Weight this run | Merge Agent Handler | StackOne | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 59 | 80 | StackOne +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 80 | 78 | Merge Agent Handler +2 |
| Agent ergonomics | 13%16.2 | 68 | 75 | StackOne +7 |
| Security & auth | 14%17.5 | 83 | 69 | Merge Agent Handler +14 |
| Payments & pricing | 10%12.5 | 55 | 38 | Merge Agent Handler +17 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 69 | 84 | StackOne +15 |
| Transparency & trust | 7%8.8 | 71 | 69 | Merge Agent Handler +2 |
| Negative events | ≤15 | 0 | -2 | |
| Total | 69.5 · B | 69.1 · B |
Facts side by side
| Fact | Merge Agent Handler | StackOne |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Merge API, Inc. | StackOne Technologies Limited |
| Hosted endpoint | https://ah-api.merge.dev/mcp | https://mcp.stackone.com/mcp |
| Transports | Streamable HTTP, HTTP | Streamable HTTP, 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 service under StackOne's SaaS Terms and Conditions. The Agent SDKs (@stackone/ai, stackone-ai) and the Defender package (@stackone/defender) are Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.stackone/mcp |
| Last release | 2026-10-05 | 2026-09-24 |
| Terms last updated | 2026-09-09 | 2026-03-30 |
| Privacy policy last updated | 2026-08-20 | 2023-12-01 |
| 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 | not found in the text |
| 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 | 30 stars, 277 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.
StackOne
StackOne's MCP server signs each person in with OAuth, lets them grant individual accounts and actions, and by default exposes two search and execute tools in place of the full catalogue. Session token URLs carry the credential in the query string for a year by default, and the Consumption Schedule and pricing page disagree on whether failed calls are billed.
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
StackOne
- Send
Accept: application/json,text/event-streamon every MCP request tohttps://api.stackone.com/mcp, by POST only. Without it the server answers 406 - In
search_executemode call{provider}_search_actionsfirst and pass the returnedaction_idto{provider}_execute_action. Never hardcode action ids - Pass the API key as the Basic auth username with an empty password, and name the linked account in
x-account-id - On 429 or 408 wait the seconds given in
Retry-After. StackOne has already retried a provider's 429 up to five times within a 60-second request lifetime - On 412 read
errorCodeanddetails.statusReasons.AccountErrorStatusneeds a person to re-authenticate the linked account
Questions
Which is better for AI agents, Merge Agent Handler or StackOne?
Merge Agent Handler and StackOne score within a point of each other on agent readiness, 69.5 (B) and 69.1 (B). StackOne leads on reliability, agent ergonomics and maintenance & community.
Do Merge Agent Handler and StackOne need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Merge Agent Handler and StackOne without installing anything?
Yes. Merge Agent Handler has a hosted endpoint at https://ah-api.merge.dev/mcp and StackOne at https://mcp.stackone.com/mcp.
Other comparisons with Merge Agent Handler or StackOne
- Composio (API + MCP) vs Merge Agent Handler
- Composio (API + MCP) vs StackOne
- Merge Agent Handler vs One
- Merge Agent Handler vs Smithery
- Merge Agent Handler vs Unified.to MCP Server
- Merge Agent Handler vs Zapier MCP (agent actions)
- One vs StackOne
- Smithery vs StackOne
- StackOne vs Unified.to MCP Server
- StackOne vs Zapier MCP (agent actions)
- letme vs Merge Agent Handler
- letme vs StackOne
Machine-readable
- This page as Markdown
/compare/merge-agent-handler-vs-stackone.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/merge-agent-handler.json·/api/v1/tools/stackone.json - From a terminal
anchor compare merge-agent-handler stackone(the CLI) - Over MCP
compare_tools {"a": "merge-agent-handler", "b": "stackone"}at/mcp, no key