In-depth architectural comparison of the Codebase Memory MCP and Booboo 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
Booboo
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Codebase Memory MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Booboo 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).
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
See and query your whole AI system as one rooted 3D knowledge graph — agents, memory, knowledge, and automations fused into a privacy-walled snapshot. MCP tools for stats, search, node dossiers, neighbors, and pathfinding; the same snapshot renders up to a million nodes in the browser. npx create-booboo
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, Booboo belongs to Knowledge & Memory using local stdio subprocess. Select Codebase Memory MCP when you need capabilities focused on knowledge & memory and Booboo when you require tools for knowledge & memory.
Grep-like text search within indexed project files.
+2 more tools listed on main page
Booboo Tools (8)
booboo_stats
Node/link counts for the whole graph, broken down by layer.
booboo_count
Counts alone, without pulling the payload — use when sizing a query.
booboo_search
Search nodes by label or id (ranked: exact > prefix > substring). Use this first to find a node's id.
booboo_node
Fetch a single node (all fields + data) by its exact id.
booboo_neighbors
The neighbourhood around a node: connected nodes + links out to `depth` hops.
booboo_path
Shortest path (chain of nodes) between two node ids; null if unreachable.
booboo_remember
Write** a durable memory — one atomic fact, tied to an agent. Appended to the journal beside the snapshot; queryable the same session, survives every rebuild.
booboo_report
Write** a report — what an agent just closed. Lands on the panel's Reports timeline.