Connect Remote MCP Servers to MCPX

Remote MCP servers are hosted outside of your environment, and MCPX can connect to them over HTTP or SSE.

You just need to provide the server name and URL when adding these servers in the MCPX Control Plane

1

Add remote server

Add each remote MCP server to your configuration with its name and URL.

{
  "notion": {
    "type": "streamable-http",
    "url": "https://mcp.notion.com/mcp"
  }
}

{
  "linear": {
    "type": "sse",
    "url": "https://mcp.linear.app/sse"
  }
}

{
  "atlassian": {
    "url": "https://mcp.atlassian.com/v1/sse"
  }
}

Tip

• Currently only two options for "type" are supported, sse or streamable-http
• "type" is optional and can be inferred according to the url:
  • the suffix /sse will infer to type sse
  • the suffix /mcp will infer to type streamable-http.

Header-based Authentication

For servers that require authentication via HTTP headers, you can add a headers object to your server configuration:

{
  "my-api-server": {
    "url": "https://api.example.com/mcp",
    "headers": {
      "Authorization": "Bearer your-api-token",
      "X-API-Key": "your-api-key"
    }
  }
}

The headers object allows you to include any custom HTTP headers needed for authentication, such as API keys, bearer tokens, or other authorization headers that your MCP server requires.

2

Authenticate

Once connected, authenticate each remote server.

• Click authenticate and follow instructions for each server.
• If a server is unreachable or returns an error, MCPX will log a warning.

Use the Control Plane to inspect connected servers and debug issues.