Waggle Mcp vs Obsidian Codex Mcp

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
W
Waggle Mcp
Abhigyan-Shekhar
🧠 Knowledge & Memory
O
Obsidian Codex Mcp
dot-RealityTest
🧠 Knowledge & Memory
SummaryPersistent 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.Local-first Obsidian vault MCP server for Codex, Claude Desktop, and other MCP clients. Works directly with markdown files, no Obsidian plugin, API key, cloud service, or running Obsidian app required. Includes read-only mode, backup-on-write, path isolation, and setup examples.
Quality signal24/100 (Emerging)25/100 (Emerging)
Install pathnpx · lowpip · high
Engagement 1 0 0 0 0 0 9
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Waggle McpView Obsidian Codex Mcp
More alternatives to Waggle McpMore alternatives to Obsidian Codex McpKnowledge & Memory category

Other servers like Waggle Mcp