MCP Obsidian vs Project MCP

A side-by-side look at the MCP Obsidian and Project MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP Obsidian logoMCP ObsidianKnowledge & Memory · Local subprocess (stdio)Universal AI bridge for Obsidian vaults using MCP. Provides safe read/write access to notes with 11 comprehensive methods for vault operations including search, batch operations, tag management, and frontmatter handling. Works with Claude, ChatGPT, and any MCP-compatible AI assistant.73GreatAuth: no auth requiredProject MCP logoProject MCPKnowledge & Memory · Local subprocess (stdio)Intent-based search over a project's documentation and todo files for AI agents. Local stdio server.64GoodAuth: no auth required

Verdict: choose MCP Obsidian for knowledge & memory work as a local process; choose Project MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

MCP Obsidian logoChoose MCP Obsidian when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like read_note, write_note, patch_note.
Explore MCP Obsidian

Project MCP logoChoose Project MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like search_project, search_docs, get_doc.
Explore Project MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Obsidian logoMCP ObsidianProject MCP logoProject MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal73/100 · Great64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,7039
Directory activity 12 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools1842

Tools & capabilities

MCP Obsidian tools 18

  • read_noteRead a note from the Obsidian vault
  • write_noteWrite a note to the Obsidian vault
  • patch_noteEfficiently update part of a note by replacing a specific string. This is more efficient than rewriting the entire note for small changes.
  • list_directoryList files and directories in the vault (includes non-note filenames, while read/write tools remain note-only)
  • delete_noteDelete a note from the Obsidian vault (requires confirmation). Supports permanent delete, vault trash, or system trash.
  • search_notesSearch for notes in the vault by content or frontmatter
  • move_noteMove or rename a note in the vault
  • move_fileMove or rename any file in the vault (binary-safe, file-only, requires confirmation)
  • read_multiple_notesRead multiple notes in a batch (max 10 files)
  • update_frontmatterUpdate frontmatter of a note without changing content
  • get_notes_infoGet metadata for notes without reading full content
  • get_frontmatterExtract frontmatter from a note without reading the content
  • +6 more on the listing page

Project MCP tools 42

  • search_projectSearch across project sources with smart intent detection. IMPORTANT: "project docs" means APPLICATION documentation (docs/ + DECISIONS.md), NOT project management. Use intent "project_docs" when user says "project docs/documents/documentation" to search application documentation. Use intent "plan" for project management (status, todos, roadmap, backlog).
  • search_docsSearch only the docs/ directory for reference documentation. Use this when the user specifically asks for "docs" or "documentation". Returns relevant documentation chunks with file paths and content snippets.
  • get_docGet the full content of a specific file. Supports files from .project/, root-level, or docs/. Use the path as returned from search results.
  • list_docsList all available documentation files organized by category. Use this to discover what documentation is available or to get an overview of the documentation structure.
  • get_doc_structureGet the complete documentation directory structure with file paths and descriptions. Useful for understanding the organization of documentation.
  • manage_project_fileSmart tool that automatically determines which project file to create or update based on context. Use this when making changes to the project - it will check project state and determine if index.md, ROADMAP.md, TODO.md, STATUS.md, or DECISIONS.md should be created/updated. This is the primary tool for managing project documentation during development.
  • check_project_stateChecks the current state of project management files. Returns which files exist (.project/index.md, ROADMAP.md, TODO.md, STATUS.md, DECISIONS.md) and provides a summary of project state. Use this before making changes to understand what exists.
  • create_or_update_roadmapCreates or updates the ROADMAP.md file in .project/ directory. Use this when planning future work, milestones, or phases. If the file exists, intelligently merges new content with existing roadmap.
  • create_or_update_todoCreates or updates the TODO.md file in .project/ directory. Use this when adding tasks, marking items complete, or updating task status. Intelligently organizes tasks into sections (In Progress, Next Up, Blocked, Completed).
  • create_or_update_statusCreates or updates the STATUS.md file in .project/ directory. Use this when updating project health, recent changes, metrics, or current phase. Automatically updates the "Last Updated" timestamp.
  • create_or_update_indexCreates or updates the index.md file in .project/ directory. This is the contract file that defines how agents should interpret sources. Use this when setting up project structure or updating source mappings.
  • create_or_update_decisionsCreates or updates the DECISIONS.md file in .project/ directory. Use this when documenting architecture decisions, trade-offs, or rationale. Helps maintain a decision log for the project.
  • +30 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

MCP Obsidian

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "bitbonsai-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "@bitbonsai/mcpvault@latest"
      ]
    }
  }
}

Project MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "project-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "project-mcp"
      ]
    }
  }
}

Frequently asked questions

MCP Obsidian is categorized under Knowledge & Memory and uses a local stdio subprocess. Project MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Obsidian for knowledge & memory work and Project MCP for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

MCP Obsidian is listed as free. Auth: no auth required. Project MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add bitbonsai-mcp-obsidian and project-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Obsidian has a quality signal of 73/100 (Great) with 12 views, 0 installs and 1,703 GitHub stars. Project MCP has 64/100 (Good) with 0 views, 0 installs and 9 GitHub stars.