Codebase Memory MCP vs Memo — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Codebase Memory MCP vs Memo
In-depth architectural comparison of the Codebase Memory MCP and Memo 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
Codebase Memory MCP
Knowledge & Memory · Local stdio
Quality: 72/100 (Great) | Auth: No auth required
Memo
Knowledge & Memory · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Codebase Memory MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Memo 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?
Choose Codebase Memory MCP 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).
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).
You have access to required keys: MEMO_GIT_SYNC_REMOTE, MEMO_EMBEDDING_BACKEND, MEMO_MLX_PATH, MEMO_API_KEY.
Primary tools included: Local Markdown file storage as source of truth, Hybrid search: vector embeddings plus BM25 keyword search, Contradiction radar to find and triage conflicting facts.
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
Local-first semantic memory server with hybrid search, plain Markdown storage, MLX or CPU embeddings, contradiction detection, time-travel history, synthesis, and cross-machine git sync.
Category & Scope
Tools & Capabilities Breakdown
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
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).
Codebase Memory MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memo belongs to Knowledge & Memory using local stdio subprocess. Select Codebase Memory MCP when you need capabilities focused on knowledge & memory and Memo when you require tools for knowledge & memory.