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 startedAPI reference
Get startedAPI reference
    • Overview
    • Quickstart
    • Model Context Protocol
  • Implementation guides
    • Tool Pack
    • Registered Users
    • MCP integration
    • Merge CLI
    • Link
    • Testing locally
  • Admin setup
    • User setup
    • Security rules
    • Authentication
    • Add OAuth credentials
  • Features
    • Magic Link
    • Remote MCP Server
    • Webhooks
    • Custom headers for MCP
  • Connectors
    • ActiveCampaign
    • Airtable
    • Amadeus
    • Amazon S3
    • Anaplan
    • Apollo
    • Articulate Reach 360
    • Asana
    • Aviationstack
    • BambooHR
    • Basecamp
    • bioRxiv
    • Bitbucket
    • Box
    • Calendly
    • Canva
    • ClickUp
    • ClinicalTrials.gov
    • Cloudflare
    • CMS Coverage
    • Confluence
    • Contentful
    • Databricks
    • Datadog
    • DocuSign
    • DoorDash
    • Dropbox
    • Duffel
    • Dynamics 365 Sales
    • Exa
    • Expensify
    • FactSet
    • Figma
    • Firecrawl
    • foursquare Foursquare
    • FreshBooks
    • Freshdesk
    • Freshservice
    • Front
    • Gamma
    • GitHub
    • GitLab
    • Gmail
    • Gong
    • Google BigQuery
    • Google Calendar
    • Google Docs
    • Google Drive
    • Google Maps
    • Google Meet
    • Google Sheets
    • Google Slides
    • Greenhouse
    • HiBob
    • HubSpot
    • Intercom
    • Jira
    • Jira Service Management
    • Klaviyo
    • Linear
    • LinkedIn
    • Make
    • Microsoft Teams
    • Miro
    • Monday.com
    • n8n
    • Notion
    • NPI Registry
    • OneDrive
    • OneNote
    • Oracle HCM
    • Outlook
    • PagerDuty
    • PayPal
    • Pipedrive
    • PubMed
    • Pylon
    • Quartr
    • QuickBooks Online
    • Ramp
    • Rootly
    • Salesforce.com logo A cloud computing company based in San Francisco, California, United States image/svg+xml Salesforce
    • SAP SuccessFactors
    • SendGrid
    • Sentry
    • ServiceNow
    • SharePoint
    • Shopify
    • Slack
    • Snowflake
    • Spotify
    • Square
    • Straker
    • Stripe
    • Teamwork.com
    • Trello
    • TripAdvisor
    • VisualPing
    • image/svg+xml SVG drawing This was produced by version 4.1 of GNU libplot, a free library for exporting 2-D vector graphics. Weather
    • Wikipedia
    • Workday
    • X
    • Yelp
    • image/svg+xml YouTube
    • golion-z-sourcefile-algaeZendesk
    • Zendesk Sell
    • Zoho CRM
    • Zoho Desk
    • Zoom
    • ZoomInfo
UnifiedAgent HandlerGateway
UnifiedAgent HandlerGateway
Resources
Log inGet a demo
On this page
  • How it works
  • Step 1: Create a new connector
  • Step 2: Tools are auto-populated
  • Step 3: Use the connector
  • Supported MCP servers
  • Unsupported MCP servers
  • Local MCP servers
  • Remote servers with dynamic OAuth
Features

Remote MCP Server

Connect a remote MCP server to create custom connectors in Merge.
Was this page helpful?
Previous

Magic Link

Next

Webhooks

Built with

Remote MCP Server support lets you create connectors in Merge by pointing to a remote MCP server. Tools are automatically discovered and can be used just like any built-in connector.

Only remote MCP servers are supported — local MCP servers and remote servers requiring OAuth are not supported at this time.

How it works

Step 1: Create a new connector

  1. Navigate to the Connectors page and click Add New.
  2. Fill in the connector details:
FieldDescription
NameA unique name that doesn’t clash with existing connectors.
Remote MCP server addressThe server’s endpoint URL.
Authorization tokenThe auth token required by the MCP server. Consult the server’s documentation to obtain this.

After submitting, the new connector is created automatically.

Step 2: Tools are auto-populated

Once the connector is created, its tools are automatically discovered and populated from the remote MCP server.

Step 3: Use the connector

  1. Add the connector to a tool pack.
  2. Invoke tools from this connector just like any other connector — responses come directly from the remote MCP server.

Supported MCP servers

Remote MCP servers are supported when they meet both of these criteria:

  • The server has a public endpoint or a private endpoint where the access token is statically specified in the config.
  • The server does not require a dynamic OAuth flow for authentication.

Unsupported MCP servers

Local MCP servers

Local servers that run as CLI commands (e.g., npx <package> <args>) are not supported. These require downloading a package locally and running it as a local process. This may be supported in the future.

Remote servers with dynamic OAuth

Remote servers that fetch access tokens dynamically via an OAuth flow are not supported, even if they have a URL-based endpoint. This would require creating OAuth apps per connector type, but Agent Handler does not know the connector until config is provided.

If you need OAuth support for a specific connector, please reach out to the Merge team to request it.