Obsidian MCP vs Qdrant MCP Server

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

	Obsidian MCP MCP Servers	Qdrant MCP Server MCP Servers
Tagline	Model Context Protocol server that lets Claude read, write, and reorganize your Obsidian vault.	Official Qdrant MCP server that turns a vector database into a semantic memory layer for Claude, Cursor, Windsurf, and any MCP client.
Category	MCP Servers	MCP Servers
Pricing	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.	Free· Free and open source (Apache-2.0). Qdrant itself can be self-hosted for free or used via Qdrant Cloud (free tier available, paid plans from ~$25/mo for managed clusters).
Model	—	FastEmbed (default: sentence-transformers/all-MiniLM-L6-v2); pairs with any MCP-capable LLM such as Claude 3.5/4, GPT-4o, or local models
Editorial score	—	—
Use cases	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	Persistent memory for Claude Desktop agentsSemantic code snippet search in Cursor and WindsurfPrivate documentation retrieval for internal LLM copilotsTeam knowledge base backed by Qdrant CloudLocal offline vector memory via QDRANT_LOCAL_PATHRead-only knowledge lookup skill for customer-support agentsCross-session context store for autonomous coding agents
Pros	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.	Official, actively maintained by the Qdrant team with 1.4k+ stars and frequent releases Two-tool surface (store/find) is small enough that models actually use it correctly Bundled FastEmbed means no separate OpenAI/Cohere embedding key is required to get started Configurable tool descriptions let you rebrand the same server as memory, code search, or docs lookup Works across the major MCP clients: Claude Desktop, Cursor, Windsurf, VS Code, and custom agents Apache-2.0 with local, Docker, and uvx install paths including a fully offline QDRANT_LOCAL_PATH mode Read-only mode makes it safe to expose a curated knowledge base without letting the model write to it
Cons	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.	Only FastEmbed is supported today, so you cannot plug in OpenAI, Cohere, or Voyage embeddings without forking Just two tools: no filtering, hybrid search, payload updates, or collection management surfaced to the model Single active collection per server process; multi-collection agents need multiple server instances or wrapping Assumes you already run and secure a Qdrant instance (self-hosted or Cloud) — not a turnkey managed product Chunking, ingestion pipelines, and re-ranking are entirely your problem; this is a thin bridge, not a RAG framework
Website	github.com	github.com

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.

Pick Qdrant MCP Server if

✅ Official, actively maintained by the Qdrant team with 1.4k+ stars and frequent releases
✅ Two-tool surface (store/find) is small enough that models actually use it correctly
✅ Bundled FastEmbed means no separate OpenAI/Cohere embedding key is required to get started
✅ Configurable tool descriptions let you rebrand the same server as memory, code search, or docs lookup

Compare a different pair →