Basic Memory vs Rag Kb — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Basic Memory vs Rag Kb
In-depth architectural comparison of the Basic Memory and Rag Kb 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
Basic Memory
Knowledge & Memory · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Rag Kb
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Basic Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Rag Kb 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 Basic Memory when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Basic Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Rag Kb belongs to Knowledge & Memory using local stdio subprocess. Select Basic Memory when you need capabilities focused on knowledge & memory and Rag Kb when you require tools for knowledge & memory.
Persistent, local-first AI memory: a semantic knowledge graph of plain Markdown files that humans and LLMs both read and write. Works with any MCP client, with optional cloud sync and team workspaces.
Local-first agent memory & knowledge service with hybrid retrieval (BGE-M3 dense vectors + BM25 via jieba, fused with RRF), document & webpage ingestion, and optional RAG answering via local Ollama. Single process, embedded ChromaDB, REST + native MCP server; fully functional offline without any LLM. Apache-2.0.