Remote Mcp Servers ↗
yesEditorial Notes
Remote MCP servers let you host tool endpoints that Claude connects to over the network, enabling shared infrastructure across teams and persistent service integrations. Pay close attention to the authentication and transport sections — remote servers use SSE or streamable HTTP rather than stdio, which changes how you handle connection lifecycle and error recovery. A frequent gotcha is failing to implement proper OAuth or token refresh flows, causing silent tool failures mid-conversation. This guide pairs well with the MCP Connector docs to compare Anthropic-hosted versus self-hosted approaches to serving tools.
Original Documentation
Several companies have deployed remote MCP servers that developers can connect to via the Anthropic MCP connector API. These servers expand the capabilities available to developers and end users by providing remote access to various services and tools through the MCP protocol.
The remote MCP servers listed below are third-party services designed to work with the Claude API. These servers are not owned, operated, or endorsed by Anthropic. Users should only connect to remote MCP servers they trust and should review each server’s security practices and terms before connecting.
Connecting to remote MCP servers#
To connect to a remote MCP server:
- Review the documentation for the specific server you want to use.
- Ensure you have the necessary authentication credentials.
- Follow the server-specific connection instructions provided by each company.
For more information about using remote MCP servers with the Claude API, see the MCP connector docs.
Remote MCP server examples#
See the original documentation for the interactive MCP servers table.
Looking for more? Find hundreds more MCP servers on GitHub.