Merge

What it is

Merge is two products under one company. The older one is a common-model integration API: one schema over HRIS, ATS, CRM, accounting and ticketing systems that B2B SaaS vendors embed to ship integrations to their own customers. The newer one, and the reason it belongs on an ops leader’s shortlist, is Agent Handler: a hosted MCP layer that lets Claude, Claude Code, ChatGPT, Cursor or an internal agent call enterprise systems through managed authentication, scoped Tool Packs, DLP scanning on every tool-call input and output, and an audit log that records identity, arguments, downstream API calls and outcome for each action.

On 1 June 2026 Merge launched Agent Handler for Employees, since renamed Merge for Workforce: it syncs employees and groups from Okta, Azure AD or any SCIM provider, maps roles to approved tools, runs every tool call under the employee’s own identity, and ships an MDM-deployed desktop client that blocks unapproved models and MCP servers on the device. A 2 June 2026 press release announced Agent Handler connectivity through the Microsoft Agent Store for Microsoft 365 Copilot.

Merge was founded in 2020, raised a $55M Series B led by Accel in October 2022 (about $74.5M total), and lists OpenAI, Perplexity, Ramp and JetBrains among Agent Handler logos. It reports SOC 2 Type II and ISO 27001.

The problem it actually removes

Two separate problems, depending on which product you buy. For a platform team building an agent, Agent Handler removes connector maintenance on the systems where it is hardest: about 30% of its connectors need vendor approval, and Merge holds signed agreements with Workday, NetSuite, Greenhouse and DocuSign. That inheritance from the integration-API business — partner access to HRIS, ATS and ERP systems that a homegrown OAuth app cannot get quickly — is the one thing Composio and Arcade do not replicate.

For IT, Merge for Workforce answers “employees already connect Claude Desktop and ChatGPT to company data; how do we govern it?” with IdP-driven access and DLP rules set per connector, per team or globally.

Pricing reality

• Free — $0 with 2,000 credits a month, unlimited users and Tool Packs. For prototyping only.
• Pro — $1,000 a month for 25,000 credits, with larger blocks up to 100,000 credits a month (prices for those blocks are not published). Overages are billed at month end; the per-credit overage rate is not published.
• Enterprise — custom. This tier carries SIEM log streaming, on-prem and managed-VPC deployment, custom connectors, forward-deployed engineers and custom SLAs.
• Merge for Workforce — quote only, priced by employee count, connectors and deployment.

The pricing page says credits are “spent with every tool call” but does not publish a credit-to-call ratio. If one call costs one credit, Pro works out to $0.04 per call — 4x Arcade’s $0.01 and roughly 130x Composio’s $0.0003. At 25,000 calls a month, Arcade’s Team plan lands near $275 and Composio Pro under $50; Merge is $1,000 before overage. The real band for a production deployment is $12,000 a year at the floor, and Enterprise once you need SIEM streaming, which most security reviews do.

Best for

The IT or security lead at a 500+ employee company whose staff already use Claude, ChatGPT or Copilot and who must approve which SaaS those assistants touch, with an audit trail and DLP on each call. The scoped case where it wins: a People Ops or Recruiting org that wants an agent reading Workday or Greenhouse, where Merge’s partner-approved connectors avoid months of vendor negotiation.

Not for

A startup prototyping an agent on Gmail, Slack and Linear at high call volume — the price per call is wrong and the catalogue is smaller than Composio’s. Teams that need event triggers or a code sandbox: Merge’s own comparison concedes it has fewer event-driven features.

Versus the alternatives

• Composio — the largest dedicated agent-tool catalogue and the cheapest per call. Pick it when an engineering team needs breadth and volume and can live with Composio holding tokens; its May 2026 incident exposed about 5,001 GitHub connections and 5,241 API keys.
• Zapier MCP — pick it when the organization already pays for Zapier and an ops generalist is wiring a low-volume assistant.
• Arcade — the fastest-growing entrant. Pick it when the requirement is per-user OAuth with per-action authorization at a quarter of Merge’s per-call price, and HRIS/ERP partner access is not the bottleneck.
• Runlayer or Obot — pick these when you want a gateway over MCP servers you already chose, rather than Merge’s own connectors. Obot is free if you run it yourself.

If none fit, put an MCP gateway in front of the vendors’ own MCP servers and accept the connector quality you get.

Watch-outs

• The credit is undefined in public. You cannot model a bill from the pricing page. Guard: get the credit-per-call schedule and the overage rate written into the order form, and run a 30-day pilot on Free with your real Tool Packs to measure credits burned per workflow before signing Pro.
• Audit and DLP stop at Merge’s console below Enterprise. SIEM streaming is an Enterprise feature, so on Pro your investigation trail lives in a vendor UI. Guard: if security requires logs in your SIEM, price Enterprise from the start instead of buying Pro and upgrading under audit pressure.
• Merge’s OAuth apps are the default. A central credential store is exactly what failed at Composio. Guard: register your own OAuth clients for write-scoped connectors, keep Tool Packs read-only until DLP rules are tested, and write the revocation runbook before launch.
• Catalogue claims vary by page. Merge cites 300+ connectors, “hundreds of enterprise systems” and 4,000+ tools in different places. Guard: list the exact systems and actions your agents need and confirm each in the Free tier before procurement.