merge.dev
Merge provides a unified integration platform for connecting to many third-party business systems through normalized APIs. It also offers Agent Handler, a tool-calling platform for AI agents that routes actions across connected SaaS tools.
Merge.dev exposes a Unified REST API, an Agent Handler management REST API, an Agent Handler MCP server, and a Merge CLI; the documented HTTP and MCP surfaces require Merge-issued bearer credentials.
- Merge Agent Handler MCP serverdetected
- Merge Unified APIdiscovered
- Merge Agent Handler APIdiscovered
- Merge CLIdiscovered
Sign in to the Merge dashboard and create or copy your API key from your Merge application settings. Use it as a bearer token in the Authorization header, as shown in Merge's authentication docs.
Create a linked account for an end customer using Merge Link or the relevant account-linking flow in your Merge implementation, then use the resulting linked account token in the X-Account-Token header, per Merge's authentication docs.
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
conventions · 0/7 published
- integrations.json——
- llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing