For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
Resources
Log inGet a demo
Get startedConnectorsAPI reference
Get startedConnectorsAPI reference
    • Overview
    • How it works
    • Quickstart
    • Use cases
  • Setup
    • Building an agent
    • Context layer for employees
    • Local development
  • Build
  • Secure
    • Security Gateway
    • Standard Entity Rules
    • Custom Regex Rules
    • Violations and alerts
    • Rule Tester
  • Observe
    • Tool Call Logs
    • API Request Logs
    • Audit Trail
    • Webhooks
    • Playground
  • Administer
    • Team and roles
    • Single sign-on
    • SCIM provisioning
    • Multi-factor authentication
    • Access Keys
    • Application Credentials
    • Billing and usage
  • Resources
    • Troubleshooting
    • FAQ

Get started

  • Overview
  • Introduction
  • Unified API
  • Linked Account
  • Merge Link
  • Use cases

Implementation

  • Sandboxes
  • SDKs
  • API access
  • Syncing data
  • Writing data
  • Data minimization
  • Supplemental data
  • Errors
  • Integration metadata

API reference

  • ATS
  • HRIS
  • Accounting
  • Ticketing
  • CRM
  • File Storage
  • Knowledge Base
  • Chat

Resources

  • Help Center
  • Merge.dev
  • Changelog
© Merge 2026Terms of usePrivacy policy
UnifiedAgent HandlerGateway
UnifiedAgent HandlerGateway
Resources
Log inGet a demo

Overview

Merge Agent Handler

Merge Agent Handler is the tool-calling platform for AI agents. It gives your agent secure, reliable access to the tools your users need - across hundreds of MCP-ready third-party services.

Authentication per end user or shared across a Group, tool scoping per agent surface, data-loss prevention on every call, and a complete Audit Trail. Enterprise-ready out of the box.

Features

Hundreds of connectors

Pre-built MCP-ready connectors for the SaaS your customers use - Salesforce, Slack, Jira, GitHub, HubSpot, NetSuite, Workday, and the rest. Tool schemas are normalized; descriptions are model-friendly.

Auth per end user

Per-user authentication or shared credentials across a Group, depending on whether each end user has their own third-party account or a tenant shares one. OAuth, API keys, and custom auth supported. Bring your own OAuth app for branding on the consent screen.

Tool Packs

A bundle of tools that determines what an agent can act on at a given point in time. Used to define tool access for an individual or an agent. Each pack is a bounded surface area you can govern, audit, and update independently.

Security Gateway

Every tool call is scanned for PII, PHI, payment data, and any custom regex you define before it leaves Agent Handler for the third party. Configure allow, redact, or block per entity, with overrides per Tool Pack.

Observability

Every tool call is captured: arguments, result, latency, the user it ran for, redactions applied, errors. Filter by user or tool. Audit log covers admin actions. Webhooks fan events out to your own pipeline.

Enterprise governance

OAuth-authenticated MCP server, SSO and SCIM for your team, custom roles, audit-trail export. The controls your security review expects, set up correctly from day one.

Start here

Quickstart

Connect Agent Handler to your IDE and make your first tool call in about five minutes.

How it works

The architecture, top to bottom. What MCP is, what Agent Handler adds, where the Security Gateway sits, what the audit log captures.

Use cases

Building an agent, context layer for employees, or local development. A short comparison so you know which path applies before you click into a setup guide.