Glossary

What Is a Remote MCP Server? Definition and How It Works

Published · Updated · 2 min read

A remote MCP server is a Model Context Protocol server you reach over the internet at a URL, instead of running it on your own computer. Your AI app connects to something like https://example.com/mcp and uses its tools, with nothing to install locally.

A simple way to picture it

Compare a desktop app with a website. A local MCP server is like software you install and run yourself. A remote one is like a website: someone else keeps it running, and you just visit the address. MCPifex's gateway at https://mcpifex.com/mcp is one example, a single URL that serves many hosted servers.

Remote vs. local

MCP has two standard transports, and they map to the two cases:

  • Local (stdio). Your AI app starts the server as a child process on your machine. Credentials come from your local environment.
  • Remote (Streamable HTTP). The server lives at one HTTP endpoint. The client sends messages to it over the network.

As of September 2026, remote servers use Streamable HTTP, which replaced the older HTTP+SSE transport (now deprecated).

How remote servers handle sessions and auth

There's no shared process to lean on, so a remote server tracks each conversation itself. It hands the client a session ID header at the start, and the client sends it back on later requests. Each request also names the protocol version it speaks.

Security is the bigger difference. Anyone who can reach the URL can try to call it, so remote servers need authentication. Many use OAuth 2.1 with PKCE, and others check a bearer token. A token belongs in the Authorization header, not the URL, unless a client leaves you no choice.

Why use a remote server?

You skip installing, updating and running the server. The catch is that building your own means writing session handling, auth and process management. A hosted gateway takes that job off you.

On MCPifex, you create an instance of a server in the portal and choose which tools are on. Your client sees only those tools, and calls to anything else are refused. Browse the marketplace, then follow the quickstart to connect. For the trade-offs, see hosted vs. self-hosted MCP.

See Model Context Protocol for the spec, MCP server for the basics, and API keys and authentication for how keys work on MCPifex.

Sources

  1. Connect to Remote MCP Servers — Model Context Protocol Docs
  2. Transports — Model Context Protocol Specification (2025-06-18)
  3. Authorization — Model Context Protocol Specification (2025-06-18)
  4. What Is a Remote MCP Server? — CircleCI Blog