Memory MCP vs Memora — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memory MCP vs Memora
In-depth architectural comparison of the 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
Memory MCP
Knowledge & Memory · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Memora
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose 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 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).
You have access to required keys: MONGODB_URI.
Primary tools included: Save, add, retrieve, and clear memories, Archive and retrieve context with tags, Relevance scoring of archived content.
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 MCP server that stores and retrieves memories from multiple LLMs using MongoDB. Provides tools for saving, retrieving, adding, and clearing conversation memories with timestamps and LLM identification.
Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
Category & Scope
Tools & Capabilities Breakdown
Memory MCP Tools (6)
Save, add, retrieve, and clear memories
Archive and retrieve context with tags
Relevance scoring of archived content
Create conversation summaries
MongoDB-backed persistent storage
Automatic context archiving based on usage thresholds
Memora Tools (6)
Persistent storage with SQLite or cloud sync (S3, R2, D1)
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).
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 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.