Cloudflare MCP Server vs MCP Memory Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Cloudflare MCP Server MCP Servers	MCP Memory Server MCP Servers
Tagline	Official suite of remote MCP servers that let Claude, Cursor, and other agents read and control your Cloudflare account.	Persistent knowledge-graph memory for Claude and other MCP clients
Category	MCP Servers	MCP Servers
Pricing	Freemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month	Free· Free and open source (MIT). Self-hosted; no vendor charges. Runs locally via npx or Docker.
Model	—	—
Editorial score	—	—
Use cases	Debugging Workers with live logs from chatDeploying and configuring Workers bindingsGrounded Q&A over Cloudflare developer docsQuerying Radar for real-time internet traffic dataPulling audit logs for compliance answersRunning a headless browser via Browser RenderingAutoRAG pipelines against R2-hosted corporaReviewing Cloudflare One CASB findingsDNS analytics and Logpush inspectionBuilding custom MCP servers from the Demo Day template	Persistent Claude Desktop memory across chatsLong-lived coding-agent project memoryLightweight personal CRM of people and companiesResearch-agent scratch knowledge graphCross-session preference and style memoryTeam convention and past-bug recall for coding assistantsStructured note-taking backend for MCP clientsLocal-first alternative to hosted memory APIs
Pros	Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development. Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install. Split into 16 focused servers so agents get relevant tools without prompt bloat. Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB. Works with any MCP-capable client - Claude Desktop, Claude Code, Cursor, Windsurf, and OpenAI Responses API. Apache 2.0 source is on GitHub, so teams can self-host, audit, or extend any server. Docs AI Search server gives agents grounded answers over the full developers.cloudflare.com corpus.	Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB Nine well-scoped tools plus a live-updating knowledge-graph Resource, so agents can both read and mutate memory Fully open source (MIT) and vendor-neutral - runs against any MCP-speaking model, not just Claude Trivial to fork or wrap for team-specific schemas since the codebase is a single small TypeScript file
Cons	Only useful if you already run on Cloudflare - it is not a general cloud MCP. Advanced capabilities inherit Cloudflare paywalls (Browser Rendering, AutoRAG, CASB, Cloudflare One all require paid plans). Write-capable tools mean a compromised or over-permissioned token can push destructive changes; scoping API tokens carefully is on you. Because the servers are hosted by Cloudflare, your agent's queries and returned data traverse Cloudflare infrastructure - not ideal for teams that want everything to stay in-VPC. OAuth and remote-MCP support is still uneven across MCP clients, so setup varies and some clients need a manual token instead. Sixteen separate endpoints can be confusing - discovery of which server owns which capability is not always obvious from client-side.	Reference-quality, not production-grade: single-file JSONL storage with no concurrency control, indexing or replication search_nodes is a plain substring match with no embeddings or semantic ranking - large graphs degrade quickly No built-in multi-user, auth or per-project isolation; a shared install mixes memories from every session The model still has to be prompted to actually call the memory tools - forgetful assistants forget to remember No web UI, visualisation or admin surface; you inspect and clean the graph by editing the JSONL yourself Only a local filesystem backend - no Postgres, SQLite or cloud sync option is shipped
Website	github.com	github.com

Pick Cloudflare MCP Server if

✅ Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development.
✅ Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install.
✅ Split into 16 focused servers so agents get relevant tools without prompt bloat.
✅ Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB.

Pick MCP Memory Server if

✅ Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client
✅ Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json
✅ Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand
✅ Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB

Compare a different pair →