How are MCP servers hosted?
Local hosting
A local MCP server runs as a program on your machine. The client launches it and talks to it through standard input and output. This setup keeps data on your computer, which many developers prefer for file or database tools.
Local servers depend on your machine having the right runtime. A Node or Python server only works if that runtime is installed and the path is correct. Updating the server means updating its dependencies on each computer that uses it.
- Runs as a process on your computer
- Talks over stdio
- Needs the local runtime and dependencies
- Keeps data on your machine
Remote hosting
Remote MCP servers run on cloud platforms or company servers. They accept HTTP requests, often with authentication, so many users can connect from different devices without installing anything locally.
Remote hosting adds security work. You need to protect tokens, limit access, and log requests. Check the vendor's security documentation before connecting sensitive data, and avoid sharing one broad token across many users.
- Runs on a web server or cloud platform
- Uses HTTP with authentication
- Works across devices
- Needs token and access controls
Common mistakes
- Connecting a remote server with broad permissions to sensitive data.
- Assuming a local server is private when it has network access.
- Ignoring server updates that change tool names.
