Chroma MCP vs Obsidian MCP

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

	Chroma MCP MCP Servers	Obsidian MCP MCP Servers
Tagline	Official MCP server that gives LLM clients direct access to the Chroma vector database.	Model Context Protocol server that lets Claude read, write, and reorganize your Obsidian vault.
Category	MCP Servers	MCP Servers
Pricing	Free· Open source (Apache 2.0). Free to run locally or self-hosted; embedding-function API keys (OpenAI, Cohere, Jina, VoyageAI, Roboflow) billed by those providers. Chroma Cloud pricing set separately by Chroma.	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	Long-term memory for Claude DesktopTeam knowledge base shared across agentsRAG over local documentsSemantic code search in Cursor or ContinueVector store for custom MCP agentsPersonal notes and journal recallMetadata-filtered document retrievalChroma Cloud access from LLM clients	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 server from the Chroma team, tracks the database's features closely Four deployment modes (ephemeral, persistent, HTTP, Chroma Cloud) from one binary Twelve well-scoped MCP tools cover the full collection and document lifecycle Supports six embedding functions including OpenAI, Cohere, Jina, and VoyageAI with per-collection persistence Zero-config install via uvx - drops into Claude Desktop or Cursor in a couple of JSON lines Apache 2.0 licensed and readable Python source; easy to fork or extend Query tools expose HNSW tuning and metadata/full-text filters, not just naive semantic search	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	You still have to run and back up the Chroma store yourself unless you pay for Chroma Cloud Command-line API key arguments are convenient but leak into process lists; env/.env path is safer but extra setup No built-in access control or multi-tenant isolation - anything the MCP client sees, it can delete Embedding-function persistence only works for collections created on Chroma v1.0.0+; older stores need migration Python-only server; teams on pure Node stacks add a runtime dependency MCP tool surface is CRUD-shaped - no higher-level RAG primitives like chunking, re-ranking, or hybrid fusion	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 Chroma MCP if

✅ Official server from the Chroma team, tracks the database's features closely
✅ Four deployment modes (ephemeral, persistent, HTTP, Chroma Cloud) from one binary
✅ Twelve well-scoped MCP tools cover the full collection and document lifecycle
✅ Supports six embedding functions including OpenAI, Cohere, Jina, and VoyageAI with per-collection persistence

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 →