MCP Obsidian vs Codebase Memory MCP

A side-by-side look at the MCP Obsidian and Codebase Memory 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 requiredCodebase Memory MCP logoCodebase Memory MCPKnowledge & Memory · Local subprocess (stdio)Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp73GreatAuth: no auth required

Verdict: choose MCP Obsidian for knowledge & memory work as a local process; choose Codebase Memory 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

Codebase Memory MCP logoChoose Codebase Memory 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 index_repository, search_graph, query_graph.
Explore Codebase Memory MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Obsidian logoMCP ObsidianCodebase Memory MCP logoCodebase Memory MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal73/100 · Great73/100 · Great
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,69747,004
Directory activity 10 views 0 installs 0 upvotes 8 views 1 installs 1 upvotes
Tools1817

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

Codebase Memory MCP tools 17

  • index_repositoryIndex a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.
  • search_graphFind symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.
  • query_graphRead-only Cypher for multi-hop, aggregation, complexity, or cross-service analysis. Default: 200 visible rows with exact/lower-bound totals and truncation; continue safely with next_cursor. graph=missed is a file tree of flagged coverage gaps; absence is not proof of completeness. Use get_graph_schema(diagnostics=full) for properties.
  • trace_pathTrace callers/callees, data flow, or cross-service paths. Defaults exclude tests and resolver evidence. Rows keep qn/hop with explicit totals, relations, and continuations.
  • get_code_snippetRead a search_graph symbol. auto bounds source and outlines large containers; full restores up to 500 lines. Source/outline pages continue; coverage_note marks gaps.
  • get_file_outlineDeclaration outline of one exact repository-relative file: optional exact label filter, source order, exact total/offset/limit paging; file/folder/container nodes excluded.
  • get_graph_schemaGet node-label and edge-type counts. diagnostics=full also lists queryable properties.
  • compare_graphsCompare two indexed snapshots: deterministic target-only additions and base-only removals of stable node/edge identities; each set capped by limit and a 512 KiB budget with exact totals and truncation reasons.
  • get_architectureCompact counts, languages, packages, entry points. Request structure, dependencies, routes, hotspots, boundaries, layers, clusters, cycles, or file_tree; path scopes a directory.
  • search_codeGraph-ranked text search: compact symbols, full bounded source, or file paths.
  • list_projectsList projects with stable paging. Identity is lean; stats adds graph sizes.
  • delete_projectDelete a project from the index
  • +5 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"
      ]
    }
  }
}

Codebase Memory MCP

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

Frequently asked questions

MCP Obsidian is categorized under Knowledge & Memory and uses a local stdio subprocess. Codebase Memory MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Obsidian for knowledge & memory work and Codebase Memory 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. Codebase Memory 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 deusdata-codebase-memory-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 10 views, 0 installs and 1,697 GitHub stars. Codebase Memory MCP has 73/100 (Great) with 8 views, 1 installs and 47,004 GitHub stars.