# Merge Agent Handler: products, MCP servers and connect URLs, one vendor page > Merge Agent Handler (merge.dev): 1 product in The GTM MCP Directory, 1 with an official MCP server, 0 answering a live handshake, 0 tools catalogued. Data baked 2026-09-27. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Vendors](../vendors/index.md) / Merge Agent Handler # Merge Agent Handler 1 product in the directory 1 official MCP server 0 live handshakes Data baked 2026-09-27 Vendor domain: [merge.dev](https://merge.dev) · vendor page id merge-dev **The rollup** - **Products**: 1, facts checked by hand 2026-09-07 - **Official MCP servers**: 1 of 1, as recorded on 2026-09-07 - **Community MCP servers**: 0 of 1 - **Live handshake**: 0 of 1 answered an MCP initialize, 0 probed, no date - **Repo local**: 0 of 1: a server you install and run yourself - **Docs only**: 0 of 1: the recorded URL is a page about the server, not the server - **Tools catalogued**: 0 named across 1 measured server, harvested 2026-09-27 - **Bench tested**: 0 of 1 here, 1 of 1,252 across the directory - **Ships a CLI**: 0 of 1 official, 0 community only, 1 none found, harvested 2026-09-27 - **GitHub organisation**: [github.com/merge-api](https://github.com/merge-api), tied to the domain with evidence 2026-09-08 A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools. **Products, 1** ### [Merge Agent Handler](../tools/merge-agent-handler.md) 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... [Official MCP](../mcp/official.md) · [Free to start](../gates/free.md) [MCP Layer](../categories/mcp-infrastructure.md) RESEARCHED - **Endpoint probe**: not probed yet, not probed - **Connect URL**: no connect URL recorded - **Tools catalogued**: 0 named, harvested 2026-09-27, catalogue dynamic, the server exposes the customer's own workspace - **last_checked**: 2026-09-07 **The gates, in plain words** 1 of 1 free to start, a solo operator gets API access without talking to anyone. The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked. **Jobs the vendor says its products do** No job tag on any product of this vendor. An empty list means nobody has tagged these entries, not that the tools do nothing. **Connect URLs** No product of this vendor records an MCP endpoint or docs URL that the probe could classify. **Command line** No CLI found for any product of this vendor by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **On GitHub** [github.com/merge-api](https://github.com/merge-api) tied to the vendor by rule 2, account website merge.dev has the vendor's domain, confidence strong - **Public repositories**: 54, forks excluded, as read on 2026-09-08 - **Mention MCP**: 2 of them - **Look like CLIs**: 0 of them - **Latest push**: 2026-09-07 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [merge-unified-skills](https://github.com/merge-api/merge-unified-skills) | other | Claude Code skills for the Merge Unified API | 0 | 2026-09-07 | | | [react-merge-link](https://github.com/merge-api/react-merge-link) | other | | 5 | 2026-08-27 | 2.4.2 | | [merge-workforce-dist](https://github.com/merge-api/merge-workforce-dist) | other | Public distribution point for the Merge Workforce desktop client (signed macOS + Windows packages). Downloads are on... | 0 | 2026-08-24 | v0.1.0-preview3 | | [react-agent-handler-link](https://github.com/merge-api/react-agent-handler-link) | other | | 0 | 2026-08-14 | | | [merge-gateway-ai-sdk-provider](https://github.com/merge-api/merge-gateway-ai-sdk-provider) | SDK | Merge Gateway provider for the Vercel AI SDK | 0 | 2026-08-11 | | Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08. **What this page does not claim** A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 1 product are among them. There is no verdict here on whether this vendor is better than another. Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).