Memory MCP vs Gingugu — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memory MCP vs Gingugu
In-depth architectural comparison of the Memory MCP and Gingugu 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: 53/100 (Good) | Auth: No auth required
Gingugu
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Memory MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Gingugu 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).
Primary tools included: Hot cache with automatic context injection, Cold semantic memory search, Automatic memory promotion and demotion.
Two-tier memory with hot cache (instant injection) and cold semantic search. Auto-promotes frequently-used patterns, extracts knowledge from Claude outputs, and organizes via knowledge graph relationships.
Persistent memory for AI coding assistants. Local SQLite, no cloud. 16 MCP tools: store, recall, search, relate, consolidate, export, and credential vault (OS keychain). Typed memories with confidence lifecycle (verified/inferred/stale/deprecated), namespaces, knowledge graph, and hybrid BM25 + semantic search via fastembed ONNX. Works with Cursor, Windsurf, Claude, and any MCP client. pip install gingugu
Category & Scope
Tools & Capabilities Breakdown
Memory MCP Tools (6)
Hot cache with automatic context injection
Cold semantic memory search
Automatic memory promotion and demotion
Project isolation by Git repository
Knowledge graph relationships between memories
Local SQLite storage and dashboard
Gingugu Tools (6)
Local SQLite persistent memory
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, Gingugu belongs to Knowledge & Memory using local stdio subprocess. Select Memory MCP when you need capabilities focused on knowledge & memory and Gingugu when you require tools for knowledge & memory.