Back home

Merge Agent Handler

sitemap 0.66
Visit source

Intro

Merge Agent Handler is Merge's tool-calling and governance platform for AI agents: connectors, per-end-user auth, an inline Security Gateway, and auditable logs between your agent and third-party systems. Site: https://www.merge.dev/ ; docs: https://docs.merge.dev/merge-agent-handler/overview ; launch post: https://www.merge.dev/blog/agent-handler .

In Merge's universal context stack it sits beside Merge Unified (customer data sync) and Merge Gateway (model routing / spend control), focused on agents that act in third-party apps on behalf of end users.

Highlights:

  • Registered Users: credential containers isolated per end user or service account;
  • Tool Packs: governed bundles of connectors/tools that bound what an agent can reach;
  • Security Gateway: scans every tools/call input/output (standard entity rules, custom regex, natural-language guardrails) to allow, redact, or block;
  • Connector Studio, rules/alerts, searchable logs, Evaluations Suite;
  • Docs cite 190+ MCP-ready third-party connectors (catalog grows over time); MCP integration supported;
  • Merge states SOC 2 Type II, ISO 27001, HIPAA, GDPR (and related) compliance posture.

Explain

Problem

Bare MCP servers often lack enterprise maintenance, per-user auth, fine-grained scopes, and DLP. LLMs can leak PII/secrets into tool calls; running OAuth/rotation per customer is expensive. Agent Handler handles onboarding, auth, rate limits, and errors while your LLM still does reasoning.

Call path (per docs)

  1. Agent lists tools from its Tool Pack;
  2. If the Registered User lacks credentials, Merge Link prompts a connect;
  3. Arguments pass the Security Gateway before the third party;
  4. Responses are scanned again, then returned—full audit trail.

Limits

  • Connector/tool coverage follows the live catalog;
  • Gateway rules must be configured per org/Tool Pack—not zero-risk by default;
  • Shares Link and credential store with Merge Unified API for teams already on Merge.

Usage

Who it's for

  • Product agents acting for customers (CRM, tickets, calendar, etc.), not only internal workforce bots;
  • Teams that need least-privilege, audit logs, and DLP for compliance (customer stories include Perplexity Enterprise and Telnyx).

Getting started

  1. Read https://docs.merge.dev/merge-agent-handler/overview and https://www.merge.dev/blog/agent-handler ;
  2. Create a free account; register users, connectors, and Tool Packs via Get started;
  3. Test locally with MCP JSON config or Merge's sample chatbot repo;
  4. Tune Security Gateway rules/guardrails and run the Evaluations Suite before production.

Advertisement