Remote MCP Server

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

Navigate to the Connectors page and click Add New.
Fill in the connector details:

Field	Description
Name	A unique name that doesn’t clash with existing connectors.
Remote MCP server address	The server’s endpoint URL.
Authorization token	The 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

Add the connector to a tool pack.
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.