Waggle Mcp vs Engram Mcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Waggle Mcp vs Engram Mcp
In-depth architectural comparison of the Waggle Mcp and Engram 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
Waggle Mcp
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Engram Mcp
Knowledge & Memory · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Waggle Mcp if you need specialized Knowledge & Memory tools running via a local process. Choose Engram 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 Waggle 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: WAGGLE_MODEL, PYTHONUTF8.
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: ENGRAM_DB, ENGRAM_EMBEDDING_URL.
Primary tools included: SQLite-backed local memory storage, Semantic search using Ollama nomic-embed-text embeddings, Keyword search fallback if embeddings are unavailable.
Persistent graph memory for AI agents. Drop a conversation turn in via observeconversation() and facts are auto-extracted, stored as typed graph nodes with local semantic embeddings (no API key). Supports temporal queries ("what did we decide last week?"), conflict detection, and context priming. One-command setup with waggle-mcp init. SQLite locally, Neo4j in production.
Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings (nomic-embed-text) with keyword fallback. remember, recall, history, forget, and stats tools. Works with Claude Desktop, Cursor, and any MCP client.
Category & Scope
Tools & Capabilities Breakdown
Waggle Mcp Tools (35)
observe_conversation
After any turn containing a decision, preference, constraint, correction, or project fact. Persists the verbatim turn first, then extracts graph nodes. Returns `turn_id`, `verbatim_stored`, `nodes_extracted`, `edges_inferred`.
query_graph
Before answering questions that may depend on prior context. Hybrid retrieval (graph + verbatim transcript) by default. Supports `as_of` for point-in-time queries.
prime_context
At the start of a new session to hydrate context from the most relevant scoped memories.
graph_diff
When the user asks what changed recently.
aggregate_graph
Broad filtered subgraph for map-reduce tasks. Use when you want a large scoped slice rather than high-precision top-K. Supports `node_types`, `tags`, `as_of`, `include_invalidated`.
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).
Waggle Mcp is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Engram Mcp belongs to Knowledge & Memory using local stdio subprocess. Select Waggle Mcp when you need capabilities focused on knowledge & memory and Engram Mcp when you require tools for knowledge & memory.