Enigma MCP
Related Servers
Alternatives to Enigma MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local MCP server that gives coding agents shared long-term memory stored as plain Markdown in your Obsidian vault, enabling hybrid recall of past project context, verified write-back of confirmed results with receipts, and automatic capture of conversations plus optional daily summaries. It runs entirely offline on CPU with no cloud calls or telemetry.MIT
- AlicenseNot gradedqualityBmaintenanceA local-first CLI and MCP server that helps you build and search a personal knowledge vault from Markdown notes, with semantic search and AI-powered features like stale note detection and session memory harvesting. It’s provider-agnostic, requires no GPU in its default mode, and exposes your vault as long-term memory to any MCP-compatible AI tool like Claude Code.47Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server exposing fast full-text and semantic search over an Obsidian vault, plus safe structured note read and write access for Claude.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA personal memory MCP server for Obsidian/markdown vaults that provides hybrid retrieval (semantic, keyword, tag, time-aware co-occurrence) and is shared across multiple AI clients.175 npmMIT
- FlicenseNot gradedqualityCmaintenanceA Python MCP server that gives Claude long-term memory and full context of everything by connecting to an Obsidian vault, enabling context retrieval, note management, and automatic graph linking.-
- AlicenseAqualityAmaintenanceLocal-first persistent memory for Claude Code and OpenAI Codex CLI. A single Rust binary captures, distills, searches, and injects project memory across sessions via hooks, MCP, CLI, and localhost REST.1533MIT
TDQS
Scored across 25 tools
Most tools target a distinct resource plus action: notes (read_note, write_note, query_notes), tasks (add_task, list_tasks), sheets (sheet_upsert/query/schema), graph (find_entity, related_notes, graph_stats, consolidate_graph) and vault maintenance (organize_vault, undo_move). The blurriest boundaries are the retrieval trio search_brain / context_bundle / recall_bundle, which all 'gather context' with different scopes, and the content-capture quartet capture / log_session / upsert_concept / write_note, which overlap in 'add prose to the vault.' Descriptions do differentiate them (digest/resume vs. search+graph vs. hybrid ranking), so confusion is limited but real.
A verb_noun convention dominates (read_note, write_note, add_task, find_entity, index_brain, consolidate_graph), but it is broken by the noun_verb sheet family (sheet_upsert, sheet_query, sheet_schema), noun_noun tools (graph_stats, librarian_status, context_bundle, recall_bundle, related_notes) and bare verbs (capture, onboard). Notably 'upsert' appears as both upsert_concept and sheet_upsert with inverted ordering. The prefixes make the families readable, but ordering is not predictable.
At 25 tools the set sits at the top of the acceptable band and feels heavy: notes, tasks, sheets, graph, search, sessions, organizing and diagnostics are all covered. Most tools earn their place in a genuinely broad vault domain, but several (recall_bundle vs context_bundle, capture vs log_session) look like they could be folded together to reduce the surface the agent must choose from.
Coverage is strong across the lifecycle: note create/read/update, task create/list, sheet upsert/query/schema, graph index/query/consolidate, hybrid search, link traversal and session logging, plus safe preview-and-apply semantics with undo. The notable gaps are deletion and task completion: there is no delete_note, no sheet row delete, and add_task/list_tasks without a way to mark a task done. These are workable around but leave the CRUD surface uneven.