The framing
Governing MCP at the edge and governing MCP in your cluster are different problems.
Cloudflare's MCP governance is serious work, and it's delivered the way Cloudflare delivers
everything: from the edge. Server Portals, AI Gateway spend limits, and Code Mode all
govern because your MCP and model traffic route through Cloudflare's network. That's the
model's greatest strength — and its sharpest boundary.
It's a different shape from the enterprise that can't route MCP traffic through a
third-party edge — regulated data, air-gapped clusters, internal credentials that can't leave
the network. And it answers a different cost question. Cloudflare meters tokens to the
model only; MCP Orchestrator meters and rates calls to the tools — and their
tokens, in your cluster, against your own rate cards. Different layers of the same stack.
The honest take
One control plane for every MCP server — internal and external.
MCP Orchestrator governs MCP servers on both sides of the perimeter. Internal servers wrapping
systems that can't leave the network, and external servers reaching third-party vendors beyond
the enterprise edge — both run through the same control plane, with credentials managed
in-cluster across every auth type and every call metered and rated against your own rate cards.
Reaching the public internet doesn't mean handing governance to someone else's edge.
"We route our agents through Cloudflare" answers where your traffic goes and what
your model tokens cost only. "Magertron governs every MCP server in our environment —
internal, external, and air-gapped — with our own keys, metered and charged back to the teams
and agents that run them" answers a question the edge can't reach from outside the network.