MCP Everything Server vs Obsidian MCP

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

	MCP Everything Server MCP Servers	Obsidian MCP MCP Servers
Tagline	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol	Model Context Protocol server that lets Claude read, write, and reorganize your Obsidian vault.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.	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	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery	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	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly	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	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault	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 MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

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 →