A team wants to share a single MCP server among multiple developers on their team. Each developer runs Claude Code locally but they want all connections to go to the same central tool server. Which transport type should they use and why?
Answer: HTTP+SSE — it supports multiple clients connecting to the same remote server, unlike stdio which forks a separate local process per user
HTTP+SSE transport connects to a server endpoint over HTTP, enabling multiple clients to connect to the same server instance. It works for both local and remote servers. Stdio transport (A) forks a new local process for each client — there's no mechanism for multiple stdio clients to share a server instance. The transport type does matter (C) — stdio is local-only by design. A named pipe (D) is not a supported configuration in the MCP stdio transport spec; stdio transport uses stdin/stdout of a forked process, not a socket file.