Local stdio MCP vs Remote MCP
When to run an MCP server as a local subprocess and when to connect to a hosted remote endpoint.
Architecture
A local stdio MCP server is a child process your client spawns and talks to over stdin/stdout. A remote MCP server is a hosted HTTPS endpoint speaking Streamable HTTP (or legacy SSE) β the client just POSTs JSON-RPC.
Deployment & updates
Stdio servers must be installed per-machine (npm, uvx, Docker) and versioned per user. Remote servers are updated once by the provider β every connected client gets the new toolset immediately.
Authentication
Local servers use ambient credentials (env vars, files). Remote servers standardize on OAuth 2.1 with PKCE and DCR, or bearer/API keys β no secrets pasted into local config files for hosted providers.
When to choose which
Choose remote for SaaS integrations (GitHub, Linear, Sentry, Stripeβ¦): first-party endpoints are more reliable than community wrappers. Choose stdio for things only your machine can see: local files, databases on localhost, private scripts.