Basic Memory vs Redm Mcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Basic Memory vs Redm Mcp
In-depth architectural comparison of the Basic Memory and Redm 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
Basic Memory
Knowledge & Memory · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
Redm Mcp
Knowledge & Memory · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Basic Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Redm 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 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).
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.
Basic Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Redm Mcp belongs to Knowledge & Memory using local stdio subprocess. Select Basic Memory when you need capabilities focused on knowledge & memory and Redm Mcp when you require tools for knowledge & memory.
Exact lookup by hash or name. O(1). Use for `Citizen.InvokeNative(0x...)` or `SCREAMING_SNAKE_CASE` names.
semantic_search
Search by behavior/concept ("teleport player", "spawn horse").
grep_docs
Regex/literal grep across raw doc files. Required for the large `rdr3_discoveries` data tables (audio_banks, ingameanims, …) which are only preview-indexed in embeddings.