# Merge Agent Handler ID: 07-merge-agent-handler Page: https://gtmmcps.com/tools/07-merge-agent-handler JSON: https://gtmmcps.com/data/tools/07-merge-agent-handler.json Documentation references: https://gtmmcps.com/docs/07-merge-agent-handler/ Category: MCP Layer MCP support: official Testing: RESEARCHED API access: free Last checked: 2026-09-07 Endpoint check: not-probed; date: Not recorded Merge's tool-calling platform for AI agents: it wraps hundreds of third-party SaaS applications as pre-built MCP-ready connectors, bundles them into scoped "tool packs" per agent, brokers per-end-user authentication, and puts a security gateway, redaction rules and an audit log in front of every tool call. ## MCP links - https://github.com/merge-api/merge-mcp - https://api.merge.dev/api/v1/tool-packs/ - https://docs.merge.dev/merge-agent-handler/build/connecting-agents/mcp-integration - https://docs.merge.dev/merge-agent-handler/overview ## Sources - https://docs.merge.dev/merge-agent-handler/build/connecting-agents/mcp-integration - https://docs.merge.dev/merge-agent-handler/overview - https://www.merge.dev/merge-agent-handler - https://www.merge.dev/pricing/agent-handler - https://github.com/merge-api/merge-mcp ## Research notes CORRECTION TO THE CANDIDATE ROW, and it matters: the address carried in CANDIDATES.md pointed at ah-api-develop.merge.dev, a development host. Merge's own documentation gives the production pattern as https://api.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp, and that is what is recorded above. Verified 2026-09-07 from the docs; no liveness probe result is recorded because the URL is per-tenant and cannot be constructed without a tool pack and a registered user. The docs also document a simplified URL for the "Agent Handler for Employees" setup, plus custom MCP servers and custom headers, so a buyer can front their own servers with the same gateway. Merge's own troubleshooting page names the two failure modes worth knowing before a bench test: a 401 on every call usually means the Bearer prefix is missing or the key belongs to the wrong environment, and session-ID mismatches require capturing and reusing the Mcp-Session-Id header. Merge sells three separate products on one brand (Unified, Agent Handler, Gateway) with three separate price lists; only Agent Handler is the MCP product and the $650/month figure that appears in Merge coverage belongs to the Unified API, not to this. 2026-09-07: the Agent Handler endpoint is per-tool-pack and per-user and templated (https://api.merge.dev/api/v1/tool-packs//registered-users//mcp), so no capability harvest can ever enumerate its tools without a customer's tool pack and registered user ids. DO NOT RE-INVESTIGATE the endpoint: the harvestable artifact is the first-party repo https://github.com/merge-api/merge-mcp (GitHub org merge-api, src/merge_mcp/server.py, last push 2025-04-30), recorded here instead. ## Named capabilities Tool names below are reported by sources. Their presence is not a successful call. ## CLI evidence Status: none-found Read current vendor documentation before configuring or running commands.