Codebase Memory Mcp vs Mcp Memory Gateway | AllMCPs
Side-by-Side Model Context Protocol Comparison
Codebase Memory Mcp vs Mcp Memory Gateway
In-depth architectural comparison of the Codebase Memory Mcp and Mcp Memory Gateway 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: 73/100 (Great) | Auth: No auth required
Mcp Memory Gateway
Knowledge & Memory · Local stdio
Quality: 60/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 Mcp Memory Gateway 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 (Freemium).
Primary tools included: PreToolUse and pre-action tool-call checks, Hard blocks for secret leaks and self-disable attempts, Warnings and logs for selected high-risk commands.
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
Pre-action gates that prevent AI coding agents from repeating known mistakes. Captures explicit feedback, auto-promotes failures into prevention rules, and enforces them via hooks.
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
Structured search by label, name pattern, file pattern, degree filters. Pagination via limit/offset.
trace_path
BFS traversal — who calls a function and what it calls (alias: `trace_call_path`). Depth 1-5.
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, Mcp Memory Gateway belongs to Knowledge & Memory using local stdio subprocess. Select Codebase Memory Mcp when you need capabilities focused on knowledge & memory and Mcp Memory Gateway when you require tools for knowledge & memory.