In-depth architectural comparison of the Codebase Memory MCP and Minirag 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
Codebase Memory MCP
Knowledge & Memory · Local stdio
Quality: 72/100 (Great) | Auth: No auth required
Minirag MCP
Knowledge & Memory · Local stdio
Quality: 55/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 Minirag 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?
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
Local-first RAG MCP server: hybrid search over a folder of your own documents
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, Minirag MCP belongs to Knowledge & Memory using local stdio subprocess. Select Codebase Memory MCP when you need capabilities focused on knowledge & memory and Minirag MCP when you require tools for knowledge & memory.
Grep-like text search within indexed project files.
+2 more tools listed on main page
Minirag MCP Tools (11)
sync_start
Reconcile the index with the document roots (or one path inside them). Returns a `jobId`; the work runs in a background thread.
sync_status
Poll a sync job started by `sync_start`.
ingest_file
Ingest or re-ingest one file, replacing any content already indexed for it.
ingest_data
Ingest text/markdown/html content the client holds, under a source id you choose.
ingest_url
Fetch an http(s) URL, convert it to Markdown, and index it.
query_documents
Hybrid search: semantic similarity plus a keyword boost for exact terms. Each hit carries `text` (the passage that matched) and `parentId`; the enclosing sections come back once each in the response's `parents` map — see [Chunking](#chunking).
read_chunk_neighbors
Read the chunks immediately before and after a search result, for context.
read_file
Read a source's entire indexed content as Markdown, reconstructed from its chunks rather than concatenated from them.
list_files
List files found on disk under the document roots, plus indexed data/url sources.
delete_file
Delete an indexed file, data item, or url item from the index.
status
Report configuration and index status, including whether the index predates the current chunking scheme. Works even when configuration is invalid.