MCP server portals now generally available
MCP server portals are now generally available to all Cloudflare customers, providing a single endpoint for approved Model Context Protocol servers with activity logging. The feature now includes gateway routing for HTTP logging and DLP scanning, Code Mode policies for tool optimization, static OAuth credentials, session management, service token authentication for machine-to-machine access, and Logpush support for SIEM integration.
MCP server portals are now generally available to all Cloudflare customers. A portal gives users one endpoint for approved Model Context Protocol (MCP) servers. Cloudflare Access logs tool, prompt, and resource activity.
Since the open beta, MCP server portals have added:
- Gateway routing for HTTP logging and data loss prevention (DLP) scanning
- Code Mode policies that control how portals reduce tool definitions and token use
- Static OAuth client credentials for providers that do not support Dynamic Client Registration
- Session management for reconnecting servers and changing authorizations from the portal
- Service token authentication for autonomous agents and machine-to-machine access
- Logpush support for exporting portal activity to external storage or a security information and event management (SIEM) system
To create a portal and connect an MCP client, refer to MCP server portals.
Source: original entry ↗