Central Memory MCP vs Memora — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Central Memory MCP vs Memora
In-depth architectural comparison of the Central Memory MCP and Memora 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
Central Memory MCP
Knowledge & Memory · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Memora
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Central Memory MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Memora 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 Central 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).
Primary tools included: Workspace-isolated entity and relation storage, Entity upserts that preserve existing IDs by name, Relation upserts using GUIDs or resolvable entity names.
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.
An Azure PaaS-hostable MCP server that provides a workspace-grounded knowledge graph for multiple developers using Azure Functions MCP triggers and Table storage.
Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
Category & Scope
Tools & Capabilities Breakdown
Central Memory MCP Tools (6)
Workspace-isolated entity and relation storage
Entity upserts that preserve existing IDs by name
Relation upserts using GUIDs or resolvable entity names
Observation storage with list conversion on read
HTTP health and readiness endpoints
Azure Table Storage data model
Memora Tools (6)
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).
Central Memory MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memora belongs to Knowledge & Memory using local stdio subprocess. Select Central Memory MCP when you need capabilities focused on knowledge & memory and Memora when you require tools for knowledge & memory.
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.