techlist.io
KREN
cloudflare

Scaling MCP adoption: Our reference architecture for simpler, safer and cheaper enterprise deployments of MCP (opens in new tab)

cloudflareci-cdmodel-context-protocolapi-designoauthdata-loss-preventionsecrets-managementmfa

Cloudflare argues that enterprise MCP adoption requires centralized governance rather than individually managed, locally hosted servers. Its reference architecture combines remote MCP servers, Cloudflare Access, MCP server portals, and AI security controls to improve visibility, authentication, policy enforcement, and performance. The company also introduces Code Mode with MCP server portals to reduce the token and context-window costs of exposing large APIs.

Centralized Remote MCP Servers

  • MCP separates the AI application from corporate credentials and APIs:
    • The MCP client connects to the LLM or agent.
    • The MCP server mediates access to internal resources.
  • Cloudflare moved away from locally hosted MCP servers because they:
    • May use unvetted software and versions.
    • Increase supply-chain and tool-injection risks.
    • Are difficult for IT and security teams to administer.
  • A centralized team manages MCP infrastructure through a shared monorepo platform.
  • Approved teams can create governed MCP servers from templates, inheriting:
    • Default-deny write controls.
    • Audit logging.
    • Automated CI/CD pipelines.
    • Secrets management.
  • Servers are deployed remotely on Cloudflare’s developer platform and custom domains, providing centralized usage visibility and global low-latency access.

Authentication with Cloudflare Access

  • Public MCP servers, such as documentation and Radar services, can remain openly accessible.
  • MCP servers connected to private corporate resources require employee authentication.
  • Cloudflare Access acts as the OAuth provider and identity layer.
  • It verifies:
    • Single sign-on.
    • Multifactor authentication.
    • IP address, location, and device-certificate context.
  • Access issues tokens that authorize users to reach protected resources.

MCP Server Portals for Discovery and Governance

  • As the number of MCP servers grew, employees needed a central way to discover authorized services.
  • Users connect their MCP client to a portal, which exposes the internal and third-party MCP servers they are permitted to use.
  • Portals provide:
    • Centralized logging.
    • Consistent policy enforcement.
    • Data loss prevention controls.
    • Access policies for users and tools.
  • Administrators can restrict both portal access and the specific tools exposed by each server.
    • Finance users might receive only read-only repository tools.
    • Engineering users on corporate devices might receive read/write capabilities.
  • Portals support MCP servers hosted on Cloudflare as well as third-party servers.
  • Cloudflare emphasizes that the relevant security and networking components can run on the same physical machine in its global network, reducing latency and avoiding unnecessary traffic transit.

Code Mode Reduces MCP Token Costs

  • The standard MCP design exposes every API operation as a separate tool.
  • For large platforms with thousands of endpoints, this exhaustive tool list consumes an agent’s context window and increases token costs.
  • Cloudflare presents Code Mode with MCP server portals as a way to address this scaling problem.
  • The provided article excerpt ends while introducing Cloudflare’s earlier use of server-side Code Mode for exposing large numbers of API endpoints.

Cloudflare’s approach recommends treating MCP as enterprise infrastructure: centrally deployed, authenticated, discoverable, policy-controlled, and monitored. Organizations adopting MCP at scale should avoid unmanaged local servers and provide reusable platforms that make secure deployment the default.