Cloudflare's MCP reference
Cloudflare published a reference architecture and launch for enterprise MCP deployments centered on Access, an AI Gateway and MCP server portals, plus a new Code Mode to reduce token costs. The post also recommends detection rules for “Shadow MCP” and frames governance as assembled from identity, routing, portals and policy. (blog.cloudflare.com)
Model Context Protocol is a standard way to let an artificial intelligence assistant call outside software, and Cloudflare on April 14 published a blueprint for running those connections inside large companies. (blog.cloudflare.com) Cloudflare’s design puts four products in the middle of that traffic: Access for identity checks, artificial intelligence Gateway for routing and logs, MCP server portals for a single entry point, and policy controls for tool-level permissions. (blog.cloudflare.com) The company also launched Code Mode for MCP server portals, which turns tool calls into code an agent can execute and keeps the prompt footprint fixed even as more services sit behind the portal. Cloudflare said an equivalent server without Code Mode could use 1.17 million tokens, while the Code Mode version exposes an entire application programming interface in about 1,000 tokens. (blog.cloudflare.com) MCP matters because it shifts artificial intelligence systems from answering questions to taking actions in payroll tools, ticket queues, code repositories, and internal dashboards. Cloudflare’s post says that turns each server into a new path to company data, which is why it recommends remote servers with centralized authentication instead of local installs on employee laptops. (developers.cloudflare.com ) (developers.cloudflare.com) Cloudflare describes local MCP servers as a shadow information technology problem and uses the term “Shadow MCP” for unauthorized servers employees connect to directly. Its guidance tells administrators to use Gateway rules to detect MCP-specific headers and traffic patterns, then route approved portal traffic through Gateway for richer Hypertext Transfer Protocol logs and data loss prevention scans. (blog.cloudflare.com) (developers.cloudflare.com) The portal layer is the operational piece of that model. Cloudflare’s documentation says a portal can group multiple MCP servers behind one endpoint, expose only selected tools to a user, and record the requests an agent makes after the connection is established. (developers.cloudflare.com) This architecture builds on products Cloudflare has been rolling out for months. The company put MCP server portals into open beta in September 2025 and earlier added remote MCP server support on Workers, with OAuth flows and transport handling built in. (blog.cloudflare.com 1) (blog.cloudflare.com 2) Cloudflare is also tying the enterprise controls to its broader agents push. Its managed catalog already lists remote MCP servers that work with clients such as Claude, Windsurf, and Cloudflare’s own artificial intelligence Playground through OAuth. (developers.cloudflare.com) The pitch is not that one product solves MCP governance. Cloudflare’s reference says companies have to assemble identity, routing, portals, and policy into one control plane before agents can use internal tools at scale. (blog.cloudflare.com)
