MCPIntermediateMCP
MCP: stdio for local, HTTP for shared
A stdio server in .mcp.json looks shared but is not; the team needs HTTP and project scope.
Transport and scope are independent decisions. stdio launches the server as a subprocess on your machine; HTTP is for remote servers or ones used by several people. SSE is the old transport: do not use it in new integrations. Local scope is personal; project scope is shared through .mcp.json. Every connected server adds tool definitions to the context, so connect only the ones you use.
Example
Personal test server → stdio + local scope. Team server → HTTP + project scope (.mcp.json). Rule: stdio + .mcp.json = a setup that looks shareable and is not.