Cloudflare MCP Server vs Obsidian MCP

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

	Cloudflare MCP Server MCP Servers	Obsidian MCP MCP Servers
Tagline	Official suite of remote MCP servers that let Claude, Cursor, and other agents read and control your Cloudflare account.	Model Context Protocol server that lets Claude read, write, and reorganize your Obsidian vault.
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). No paid tiers; users only pay for their own Obsidian license if they choose Commercial/Sync/Publish add-ons.
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	Draft new Obsidian notes from a Claude Desktop chatBulk rename or consolidate tags across a vaultSearch notes and stitch together related materialRefactor folder structure by moving notes programmaticallySummarize or rewrite existing notes in placeExpose multiple local vaults to a single AI assistantWire an Obsidian vault into Cline, Cursor, or a custom MCP agent
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.	Twelve concrete note and tag tools cover the everyday read/write/search operations most Obsidian users need. Runs entirely locally over stdio — vault contents never leave the machine and no API keys or accounts are required. Trivial install: one npx command in Claude Desktop config, or a single Smithery CLI line. Multi-vault aware — expose several vaults and let the assistant list and target them explicitly. MIT-licensed TypeScript source that is small enough to audit or fork before pointing an agent at your notes. Works with any MCP client, not just Claude Desktop, so the same server plugs into Cline, Cursor, Zed, or custom agents.
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.	Full write access with no built-in undo — a bad agent call can rename, move, or delete notes irreversibly, so backups or git are mandatory. Does not talk to the running Obsidian app or its plugin API: no Dataview queries, no canvas, no graph view, no plugin actions. Search is plain text over Markdown, not the semantic/embedding search users may expect from an 'AI' Obsidian integration. Solo-maintained hobby project — the README itself notes tools are 'tested but not exhaustively' and development is ongoing. No first-party support for the Obsidian mobile app or Obsidian Sync-specific features. Requires Node.js 20+ locally, which is friction for non-technical Obsidian users used to installing community plugins from inside the app.
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 Obsidian MCP if

✅ Twelve concrete note and tag tools cover the everyday read/write/search operations most Obsidian users need.
✅ Runs entirely locally over stdio — vault contents never leave the machine and no API keys or accounts are required.
✅ Trivial install: one npx command in Claude Desktop config, or a single Smithery CLI line.
✅ Multi-vault aware — expose several vaults and let the assistant list and target them explicitly.

Compare a different pair →