Fixes › Guides
Where to host a remote MCP server
Most MCP servers run locally: your client starts them with npx or uvx and talks to them over stdio. You only need hosting if you want a remote server that several people, devices, or web-based clients can reach over HTTP.
Disclosure: some links on this page are affiliate links. If you sign up through them, we may earn a commission at no extra cost to you. Details.
Do you actually need hosting?
- No, if you're the only user and the server runs on your own machine. Keep it local; it's simpler and free.
- Yes, if you're sharing a server with a team, using a client that can only connect to URLs, or exposing your own product's tools to users.
What the host needs to support
- A long-running web process (Node.js or Python) listening on HTTPS, because remote MCP uses the Streamable HTTP transport.
- Secrets stored as environment variables, not in your code (why this matters).
- Authentication in front of the server if it can touch private data. The MCP spec describes OAuth-based authorization.
Main options
- App platforms that deploy a GitHub repo or Dockerfile as a web service, for example Railway (affiliate link; new accounts that sign up through it get $20 in Railway credits, per Railway), Render, or Fly.io. Easiest if you already have a working server.
- Serverless / edge, for example Cloudflare's remote MCP server guide. Good for lightweight servers; check its runtime limits first.
- A VPS you manage yourself (any Linux server). Most control, but you handle updates, HTTPS, and security.
Compare current pricing and limits on each provider's own site before choosing; they change often. Whichever you pick, test the URL with your client (e.g. claude mcp add --transport http name https://your-url/mcp) before sharing it.