In-depth architectural comparison of the Codebase Memory Mcp and Vlk MemAct 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
Vlk MemAct
Knowledge & Memory · Local stdio
Quality: 28/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Codebase Memory Mcp if you need specialized Knowledge & Memory tools running via a local process. Choose Vlk MemAct 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
Stateful memory for AI agents. Temporal awareness, error loop detection, and preventive constraints.
Codebase Memory Mcp is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Vlk MemAct belongs to Knowledge & Memory using local stdio subprocess. Select Codebase Memory Mcp when you need capabilities focused on knowledge & memory and Vlk MemAct when you require tools for knowledge & memory.