In-depth architectural comparison of the Codebase Memory Mcp and MemoryPlugin 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
MemoryPlugin
Knowledge & Memory · Remote HTTP/SSE
Quality: 42/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 MemoryPlugin if your workspace requires Knowledge & Memory integration with remote web transport. 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
Give every AI you use one shared, permanent memory. Store once, recall in whichever AI you open.
Codebase Memory Mcp is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, MemoryPlugin belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select Codebase Memory Mcp when you need capabilities focused on knowledge & memory and MemoryPlugin when you require tools for knowledge & memory.