Memora vs Booboo — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memora vs Booboo
In-depth architectural comparison of the Memora and Booboo 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
Memora
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Booboo
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Memora if you need specialized Knowledge & Memory tools running via a local process. Choose Booboo 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 Memora when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: MEMORA_DB_PATH, MEMORA_STORAGE_URI, CLOUDFLARE_API_TOKEN, AWS_PROFILE, AWS_ENDPOINT_URL, MEMORA_CLOUD_ENCRYPT, MEMORA_ALLOW_ANY_TAG, MEMORA_GRAPH_PORT.
Primary tools included: Persistent storage with SQLite or cloud sync (S3, R2, D1), Hierarchical memory organization with sections and subsections, Semantic search using TF-IDF, sentence-transformers, and OpenAI embeddings.
Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
See and query your whole AI system as one rooted 3D knowledge graph — agents, memory, knowledge, and automations fused into a privacy-walled snapshot. MCP tools for stats, search, node dossiers, neighbors, and pathfinding; the same snapshot renders up to a million nodes in the browser. npx create-booboo
Category & Scope
Tools & Capabilities Breakdown
Memora Tools (6)
Persistent storage with SQLite or cloud sync (S3, R2, D1)
Hierarchical memory organization with sections and subsections
Semantic search using TF-IDF, sentence-transformers, and OpenAI embeddings
Knowledge graph visualization with Mermaid and live graph server
Memory linking with typed edges and AI-powered deduplication
RAG-powered chat interface for memory querying and updates
Booboo Tools (8)
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).
Memora is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Booboo belongs to Knowledge & Memory using local stdio subprocess. Select Memora when you need capabilities focused on knowledge & memory and Booboo when you require tools for knowledge & memory.
Node/link counts for the whole graph, broken down by layer.
booboo_count
Counts alone, without pulling the payload — use when sizing a query.
booboo_search
Search nodes by label or id (ranked: exact > prefix > substring). Use this first to find a node's id.
booboo_node
Fetch a single node (all fields + data) by its exact id.
booboo_neighbors
The neighbourhood around a node: connected nodes + links out to `depth` hops.
booboo_path
Shortest path (chain of nodes) between two node ids; null if unreachable.
booboo_remember
Write** a durable memory — one atomic fact, tied to an agent. Appended to the journal beside the snapshot; queryable the same session, survives every rebuild.
booboo_report
Write** a report — what an agent just closed. Lands on the panel's Reports timeline.