cfdocs__*
Cloudflare's MCP docs server — a native 2026-07-28 stateless peer, proxied zero-copy.
fold is the one. fold.run is the execution.
The enterprise
MCP gateway.
One governed endpoint between every MCP client and every MCP server. Federation, auth, policy, era translation, caching, and audit — automatically aligned with the MCP specification, SEPs, and SDKs.
# every team's servers, one governed endpoint
{
"upstreams": [
{ "id": "github-tools", "url": "…", "namespace": "gh" },
{ "id": "ml-search", "url": "…", "namespace": "search", "protocol": "legacy" }
],
"auth": { "mode": "required", "…": "…" },
"policy": { "defaultDecision": "deny", "…": "…" }
}40/40official MCP conformance scenarios, on Node.js and Cloudflare Workers
~1.8 msp50 added latency on the zero-copy passthrough path
2026-07-28native spec version, with bidirectional legacy translation
Apache-2.0open source, on GitHub
See it live.
demo.fold.run federates three real servers from three protocol eras behind one endpoint. Point any MCP client at it.
# three servers, three eras, one governed endpoint — no signup, no key
https://demo.fold.run/mcp
tools/list → cfdocs__* · git__* · jobs__*
jobs__start_job → resultType "task" · taskId "demo-job-7"
tasks/get → "completed" — every poll routed to the owning server
subscriptions/listen → one stream, every upstream's notifications, origin-taggedgit__*
GitMCP — a stateful 2025-era server, translated live through a held session in a Durable Object. Clients never notice.
jobs__*
A task-minting demo server. Start a job, poll it, cancel it, or subscribe to its status — long-running work flowing across the federation.
One gateway. A family of problems.
Most deployments start with one of these and grow into the others — they all ride the same config file.
Unify a federation
Acquisitions, child orgs, and teams each ship their own MCP servers — any language, any SDK. fold presents them as one virtual server with namespaced tools. No team rewrites anything.
Draw the security boundary
One choke point for authentication, deny-by-default tool allowlists, per-principal visibility, and an audit event for every request — including the denials.
Insulate protocol eras
fold speaks 2026-07-28 natively and translates in both directions. Teams migrate off legacy SDKs on their own schedule; clients never notice.
Run tasks across the federation
Long-running work flows through fold: task polls and updates route to the server that owns the task, tasks/list merges every org, and one subscriptions/listen stream carries all upstream notifications.
Broker credentials
Clients hold one token with fold as audience; fold exchanges it per upstream (RFC 8693) or injects service credentials. API keys never reach agents.
Protect fragile services
Response caching, global and per-upstream rate limits, and circuit breakers stand between agent traffic storms and your internal systems.
Govern vendor MCP servers
Put third-party and SaaS MCP endpoints behind your own auth, policy, and audit — instead of scattering per-user API keys across every client.
Expose tools outward, carefully
Offer partners a curated, policy-scoped subset of internal tools on one hardened endpoint — self-hosted in your VPC or at the edge.
Stay current automatically
A daily watcher tracks the MCP spec, SEPs, and SDKs, opening human-reviewed PRs. The official conformance suite gates every merge.
Start where it hurts.
A single passthrough upstream in front of your most-used server is one config file away. Governance grows from there.