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
Token-based authentication with required prefix “Bearer”
Request
Identifier for the connector. Lowercase letters, digits and underscores. Derived from name when omitted.
Additional non-secret headers sent on every request. Write-only: the caller is the system of record for header state.
Defaults to {"type": "none"}.
Response
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.
oauth only, otherwise null. The connector has no tools until someone completes this link.