Skip to navigation

Register a remote MCP server

Registers a remote MCP server as a connector. For none and secret, Merge completes the MCP handshake against the server before anything is written, so either a connector exists with its tools discovered or nothing does.

auth.type accepts none, secret and oauth.

With secret, set auth.auth_scope to INDIVIDUAL to have each registered user enter their own full header value through Link, including any Bearer prefix.

With oauth, each registered user authorizes through Link. Every field in auth.oauth is optional. Merge reads missing endpoints from the server’s OAuth authorization server metadata, following its protected resource metadata (RFC 9728) when the server delegates OAuth to a separate identity provider, and, without a client_id, registers a client through the server’s dynamic client registration endpoint.

The server lists its tools only to an authorized user, so an oauth connector is created with no tools and the response carries a setup.magic_link_url. Open it and complete OAuth: Merge lists the tools with that sign-in and saves them on the connector. The first registered user to authorize the connector by any route does the same. The link expires; get a fresh one from the connector’s page in the dashboard.

Authentication

AuthorizationBearer

Token-based authentication with required prefix “Bearer”

Request

This endpoint expects an object.
namestringRequired<=100 characters
Display name for the connector.
urlstringRequiredformat: "uri"
HTTPS URL of the remote MCP server. Immutable once set.
slugstringOptional

Identifier for the connector. Lowercase letters, digits and underscores. Derived from name when omitted.

headersmap from strings to stringsOptional

Additional non-secret headers sent on every request. Write-only: the caller is the system of record for header state.

authobjectOptional

Defaults to {"type": "none"}.

Response

idstring
Unique identifier for the Connector
namestring
Name of the Connector
slugstring
Slug identifier for the Connector
descriptionstring
Description of what the Connector does
source_urlstring or null
URL to the Connector's source website
logo_urlstring
URL to the Connector's logo image
categorieslist of strings or null
Categories this connector belongs to
auth_optionslist of objectsRead-only
Authentication options available for this connector
toolslist of objectsRead-only

List of available tools for this connector. By default each tool includes only name, description, and credit_type; pass include_tool_details=true on the detail endpoint to also include input_schema, output_schema, annotations, scopes, and endpoints.

setupobject or null

oauth only, otherwise null. The connector has no tools until someone completes this link.

Errors

409
Conflict Error