Codebase Memory MCP vs Easy Obsidian MCP
A side-by-side look at the Codebase Memory MCP and Easy Obsidian MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codebase Memory MCP for knowledge & memory work as a local process; choose Easy Obsidian 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?
Choose 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.
Choose Easy Obsidian MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OBSIDIAN_API_KEY. - You want tools like
obsidian_simple_search, obsidian_dataview_search, obsidian_get_file_content.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 73/100 · Great | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | OBSIDIAN_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 47,352 | 17 |
| Directory activity | 8 views 1 installs 1 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 17 | 6 |
| Full listing | View Codebase Memory MCP | View Easy Obsidian MCP |
Tools & capabilities
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
Easy Obsidian MCP tools 6
obsidian_simple_searchsimple search for documents matching a specified text query across all files in the vault. use this tool when you want to do a simple text searchobsidian_dataview_searchexecute a dataview query language (dql) query. dql is a powerful, sql-like language for querying obsidian notes based on metadata (frontmatter, inline fields), tags, folders, links, file properties (name, path, dates), and tasks. use it to filter, sort, group, and transform data from your obsidian vault. **key difference from sql:** dql executes queries sequentially, line by line, passing results between commands. this allows multiple 'where', 'sort', or 'group by' steps, unlike declarative sql. **finding people/names:** - search note titles: 'table file.name where contains(file.name, "ben")' - find notes linking to person: 'list from [[Ben]]' - search by person tag: 'list from #person/ben' **common patterns:** - get note metadata: 'table file.name, file.mtime from "NOTENAME"' - search by tag: 'list from #tag' - folder search: 'list from "folder/"' - backlinks: 'list from [[FILENAME]]' - all notes: 'list from ""' this tool is especially good at finding relationships between notes, metadata searches, and structured queries. use it when simple text search doesn't find what you need. see dataview documentation for full syntax: https://blacksmithgu.github.io/obsidian-dataview/obsidian_get_file_contentretrieves the full content of a specific file from the obsidian vault.obsidian_list_fileslists files and folders within a specified directory in the obsidian vault. if no directory is specified, lists items in the vault root.obsidian_fuzzy_searchfuzzy search for notes using approximate matching. works even when obsidian api is unavailable. great for finding notes when you're not sure of exact spelling or phrasing.obsidian_graph_searchanalyze links and connections between notes. finds orphaned notes, builds link graphs, and discovers note relationships. works without obsidian api.
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.
Codebase Memory MCP
{
"mcpServers": {
"deusdata-codebase-memory-mcp": {
"command": "npx",
"args": [
"-y",
"codebase-memory-mcp"
]
}
}
}
Easy Obsidian MCP
{
"mcpServers": {
"louis030195-easy-obsidian-mcp": {
"command": "npx",
"args": [
"-y",
"@louis030195/mcp-obsidian"
],
"env": {
"OBSIDIAN_API_KEY": "YOUR_OBSIDIAN_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Codebase Memory MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Easy Obsidian MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Codebase Memory MCP for knowledge & memory work and Easy Obsidian 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.
Codebase Memory MCP is listed as free. Auth: no auth required. Easy Obsidian MCP is listed as free. Auth: api key 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 deusdata-codebase-memory-mcp and louis030195-easy-obsidian-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codebase Memory MCP has a quality signal of 73/100 (Great) with 8 views, 1 installs and 47,352 GitHub stars. Easy Obsidian MCP has 60/100 (Good) with 6 views, 0 installs and 17 GitHub stars.