Enabled secure remote MCP server connections via OAuth 2.1 and streamable HTTP, eliminating local setup requirements.
Product AnnouncementEnabled secure connection to remote MCP servers from Claude Code, allowing developers to connect favorite dev tools and data sources without local server setup.
MCP servers can now run on central infrastructure (internal servers, cloud services, SaaS platforms) and be accessed remotely by Claude Code instances. This enables centralized tool management: organizations run MCP servers once, hundreds of developers connect to them. No local server setup required.
Remote MCP servers use OAuth 2.1 to authenticate and authorize access securely. This is industry-standard secure authentication that integrates with existing enterprise identity systems (Okta, Azure AD, etc.). Organizations can control which developers access which tools through existing access control infrastructure.
Remote MCP communicates over HTTP with streaming support, enabling efficient real-time communication between Claude Code and remote servers. Streaming is critical for large tool responses or data transfers. HTTP transport ensures compatibility with existing network infrastructure, firewalls, and proxy systems.
Remote MCP enables enterprise-scale deployment patterns: security teams run centralized MCP servers with access controls, developers connect to them as part of their development environment. This is the platform infrastructure layer — MCP becomes enterprise tooling infrastructure, not just developer tools.