In-depth architectural comparison of the Obsidian MCP Server and Codebase Memory MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Obsidian MCP Server
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Codebase Memory MCP
Knowledge & Memory · Local stdio
Quality: 72/100 (Great) | Auth: No auth required
Verdict Summary: Choose Obsidian MCP Server if you need specialized Knowledge & Memory tools running via a local process. Choose Codebase Memory MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
O
Choose Obsidian MCP Server when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Filesystem-based MCP server for Obsidian vaults — read, search, and edit notes, no app required.
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-mcp
Category & Scope
Tools & Capabilities Breakdown
Obsidian MCP Server Tools (24)
read_note
Read a note's content and metadata
write_note
Create or update a note
list_directory
List files and subdirectories
get_frontmatter
Read YAML frontmatter from a note
update_frontmatter
Set or remove frontmatter keys (format-preserving)
manage_tags
Add or remove a tag on a note
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Obsidian MCP Server is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Codebase Memory MCP belongs to Knowledge & Memory using local stdio subprocess. Select Obsidian MCP Server when you need capabilities focused on knowledge & memory and Codebase Memory MCP when you require tools for knowledge & memory.
Move a note to `.obsidian-mcp/trash` (requires confirm); pass `permanent: true` to hard-delete instead
move_note
Move or rename a note within the vault (requires confirm); rewrites unambiguous inbound links by default
search_notes
BM25 full-text search with ranked results and match snippets
+12 more tools listed on main page
Codebase Memory MCP Tools (14)
index_repository
Index a repository into the graph. Auto-sync keeps it fresh after that.
list_projects
List all indexed projects with node/edge counts.
delete_project
Remove a project and all its graph data.
index_status
Check indexing status of a project.
search_graph
Structural, BM25, and semantic search. Page structural rows with `offset`/`limit` and ranked semantic rows independently with `semantic_offset`/`semantic_limit`.
trace_path
BFS traversal — who calls a function and what it calls (alias: `trace_call_path`). Depth 1-5.
detect_changes
Map git diff to affected symbols + blast radius with risk classification.
query_graph
Execute Cypher-like graph queries (read-only).
get_graph_schema
Node/edge counts, relationship patterns, property definitions per label. Run this first.
get_code_snippet
Read source code for a function by qualified name.