Claude Desktop Remote MCP: Add a Custom Connector

In short: in Claude Desktop a remote MCP server is not configured in claude_desktop_config.json: you add it as a custom connector from the settings, pasting the server's HTTPS address. The connector belongs to your whole account, so you also find it on claude.ai and in the mobile app.

Local MCP vs remote MCP

If you search for “Claude Desktop remote MCP” you usually want the second column: using a server that is not on the computer you are typing on, or using your own PC when you are not in front of it.

Adding the connector, step by step

1. Get the remote MCP server's address. With MCP DeskManager it is the tunnel address the app shows after installation: already on HTTPS, with authentication, and no ports to open.
2. In Claude Desktop open Settings → Connectors.
3. Choose Add custom connector, type a recognisable name and paste the address.
4. Confirm the connection: the server's authorization opens; after you approve, the connector shows as active.
5. In a new chat check that the connector is on in the tools menu, then ask the PC for something.

Adding custom connectors requires a Claude plan that includes them; in company workspaces an admin may need to enable them.

Common problems

The connector does not connect

Check that the address is complete and that the PC running the server is on and online. With DeskManager the tunnel comes back by itself after a reboot.

I edited claude_desktop_config.json but the remote server does not show up

That file is for local servers started by Claude Desktop. Remote servers are added from the settings as connectors.

The connector is there but Claude does not use its tools

Make sure it is enabled in the chat (tools menu) and ask explicitly, for example “use my PC to…”.