WikiMoth MCP Server
Related Servers
Alternatives to WikiMoth MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables semantic search and note management for Obsidian vaults via the Model Context Protocol, allowing LLMs to search, read, and index notes, PDFs, and web pages locally.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cursor, Zed, and Windsurf to recall associative context from a folder of markdown notes, combining vector search entry points with one-hop [[wikilink]] graph expansion and cross-encoder reranking over a single SQLite file. It also appends a zero-token per-turn ledger of asks, files, tools, and decisions that agents can consult across sessions.154 PyPI13MIT
- AlicenseAqualityBmaintenanceExposes local markdown documentation, notes, and knowledge bases to AI tools via the Model Context Protocol without embeddings or uploading.422 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, read, create, and maintain a local-first knowledge base using hybrid retrieval and Markdown note management through the Model Context Protocol.11 npm1MIT
- AlicenseAqualityBmaintenanceExposes a typed, provenance-aware knowledge graph over an Obsidian vault to coding agents over MCP, so they can trace what grounds a claim, compute which other notes a change makes wrong, surface contradictions and admitted gaps, and assemble a task-specific token-budgeted subset of the vault. Indexing, retrieval, and impact analysis run with zero third-party runtime dependencies beyond the Python standard library.10MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables semantic search and content retrieval from local Obsidian vaults through the Model Context Protocol. It allows AI assistants to query notes by meaning, filter by tags, and access full note content for enhanced knowledge integration.MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: recall retrieves note-chains; status reports vault metadata; list_duplicates, list_conflicts, list_lint, and list_fading each surface a different kind of maintenance issue; supersede performs the single write action. No two tools could be reasonably confused.
The naming is predominantly snake_case with a consistent list_ prefix for the four inspection tools, and recall/supersede are clear action verbs. The one deviation is 'status', which is a noun rather than a verb_phrase, though it is still intuitive.
Seven tools is well-scoped for the server's purpose of maintaining and recalling from a WikiMoth vault. Each tool addresses a distinct need without redundancy, and the count feels neither thin nor bloated.
The set covers the key lifecycle: detect issues (duplicates, conflicts, lint, fading), adjudicate via recall/status, and resolve via supersede. Minor gaps exist such as no direct 'get_note' or vault-wide listing tool, but recall likely covers most retrieval needs and the core maintenance loop is complete.