> Each MCP server still needs to handle auth differently depending on what it's connecting to. Setting aside expected criticism about this being some middlewar

> Each MCP server still needs to handle auth differently depending on what it's connecting to. Setting aside expected criticism about this being some middleware layer, but we’ve launched a solution to this problem: An MCP “SSO”, where you install and auth your MCP servers into profiles (collections of servers), which we virtualize into a single MCP server with only a single OAuth flow — simplifying the experience substantially for both the user of the MCP servers and the clients connecting to them. https://docs.mcp.run/blog/2025/05/14/mcp-sso/ https://docs.mcp.run/blog/2025/05/14/mcp-sso/