Understanding Remote MCP Servers
Remote MCP servers function similarly to local MCP servers but are hosted on the internet rather than your local machine. They expose tools, prompts, and resources that Claude can use to perform tasks on your behalf. These servers can integrate with various services such as project management tools, documentation systems, code repositories, and any other API-enabled service. The key advantage of remote MCP servers is their accessibility. Unlike local servers that require installation and configuration on each device, remote servers are available from any MCP client with an internet connection. This makes them ideal for web-based AI applications, integrations that emphasize ease of use, and services that require server-side processing or authentication.What are Custom Connectors?
Custom Connectors serve as the bridge between Claude and remote MCP servers. They allow you to connect Claude directly to the tools and data sources that matter most to your workflows, enabling Claude to operate within your favorite software and draw insights from the complete context of your external tools. With Custom Connectors, you can:- Connect Claude to existing remote MCP servers provided by third-party developers
- Build your own remote MCP servers to connect with any tool
Connecting to a Remote MCP Server
The process of connecting Claude to a remote MCP server involves adding a Custom Connector through the Claude interface. This establishes a secure connection between Claude and your chosen remote server.1
Navigate to Connector Settings
Open Claude Desktop or Claude in your browser, then navigate to the settings page:
- Desktop: Either use the keyboard shortcut
Ctrl+Commaor click the top-left menu icon
, hover over “File”, and select “Settings” - Browser: Either use the keyboard shortcut
⌘⇧,(macOS) or click on your profile icon, and select “Settings” from the menu
2
Add a Custom Connector
In the Connectors section, click the “Add” button at the top-right of the window, then select “Add custom connector” from the dropdown. This begins the connection process. To follow along, copy/paste the URL below:
A dialog will appear prompting you to enter the remote MCP server URL. This URL should be provided by the server developer or administrator. Enter the complete URL, ensuring it includes the proper protocol (https://) and any necessary path components.
After entering the URL, click “Add” to proceed with the connection.
Example Remote Server


3
Complete Authentication
Most remote MCP servers require authentication to ensure secure access to their resources. The authentication process varies depending on the server implementation but commonly involves OAuth, API keys, or username/password combinations.