What is a remote MCP server?

Written by Blake Folgado, last update:

A remote MCP server is a Model Context Protocol server that runs on someone else's infrastructure and is reached over HTTPS at a URL, rather than being launched as a local process on your machine.

The Model Context Protocol defines two transports in common use. A local (stdio) server is a command the client spawns — npx -y toolrouter-mcp, for example — and talks to over standard input and output. A remote server is an HTTPS endpoint: the client is configured with a URL and connects to it, typically using streamable HTTP.

Why it matters

Remote servers work where you cannot run a process at all. Claude chat on the web and on mobile, ChatGPT apps and Microsoft Copilot Studio can only reach a URL — there is no terminal to run a command in. Remote also means no Node.js requirement, no local install to keep updated, and one server version for everyone.

The trade-offs are real. A remote server sees the arguments you send it and runs from its own network, not your laptop's, so it cannot reach your local files or private network unless you give it a path. Connect only to servers you trust, and review what each tool is permitted to do — especially anything that writes, deletes, spends or contacts people.

Local servers keep their own advantages: access to your filesystem, no third-party network hop for the transport, and offline capability for tools that need none.

How ToolRouter does it

ToolRouter is available both ways. The remote endpoint is https://api.toolrouter.com/mcp (Claude chat uses the policy-filtered https://api.toolrouter.com/mcp/anthropic). The local bridge is the toolrouter-mcp npm package, run with npx -y toolrouter-mcp. Both provision an anonymous account on first connect; neither needs an API key pasted in to start.