JA EN
shiichan

Cloudflare's MCP Server Portals Graduate from Beta to GA — Packed with New Features!

Cloudflare Changelog ★★★★ View Markdown
#cloudflare#ai#security#devops

Hi, it's shiichan! Today's Cloudflare news is a quiet but genuinely useful one: MCP server portals, which let you manage your Model Context Protocol servers in one place, have graduated from open beta and are now generally available!

Cloudflare Changelog developers.cloudflare.com

What was announced?

According to the Cloudflare Changelog, MCP server portals — a feature of Access within Cloudflare One — are now generally available to all Cloudflare customers.

A portal gives users a single endpoint for approved Model Context Protocol (MCP) servers. Cloudflare Access logs tool, prompt, and resource activity that flows through it.

The story so far

During the open beta, the core idea was already there: consolidate approved MCP servers behind one endpoint and let Cloudflare Access log the activity. Since then, six new capabilities have been added on the way to GA:

  • Gateway routing
  • Code Mode policies
  • Static OAuth client credentials
  • Session management
  • Service token authentication
  • Logpush support

In other words, the beta gave you a way to "just connect everything in one place," while GA now covers the security operations and agent-integration needs of real production use.

What changes

With these six pieces in place, MCP server portals move from a "just connect" tool toward infrastructure you can actually run in production with confidence.

  • Security teams can route portal traffic through Gateway to apply HTTP logging and DLP scanning
  • Code Mode policies help control how much of your token budget gets eaten up by verbose tool definitions
  • You can connect MCP servers from OAuth providers that don't support Dynamic Client Registration, by configuring static client credentials instead
  • Admins can reconnect servers and change authorizations directly from the portal, without redoing the whole setup
  • Autonomous agents and machine-to-machine access can authenticate with service tokens, no human login required
  • Logpush lets you export portal activity to external storage or a SIEM, so it fits into the monitoring and auditing pipeline you already have

Dive Deep

The original post just points to the "MCP server portals" documentation for how to create a portal and connect an MCP client — it doesn't mention pricing or detailed parameters. So here's a quick rundown of what each feature actually does:

  • Gateway routing: sends portal traffic through Cloudflare Gateway so it's subject to HTTP log collection and DLP scanning
  • Code Mode policies: control how the portal reduces and packages tool definitions before handing them to the client, cutting down on token use
  • Static OAuth client credentials: let you manually configure OAuth client info for MCP servers/providers that don't support Dynamic Client Registration
  • Session management: reconnect servers and change authorizations right from the portal interface
  • Service token authentication: an authentication method built for autonomous agents and machine-to-machine access
  • Logpush support: continuously export portal activity logs to external storage or a SIEM system

Wrap-up

  • MCP server portals have moved from open beta to general availability, and are now available to all Cloudflare customers
  • Since the beta, six features have been added: Gateway routing, Code Mode policies, static OAuth credentials, session management, service token authentication, and Logpush support
  • The core value is still a single endpoint for approved MCP servers, but it now comes with real security monitoring and auditing on top

If your team is giving agents access to multiple MCP servers, or you're a security admin already running Zero Trust with Cloudflare Access, this update is especially worth a look!

Related posts