wiki-compiler
Related Servers
Alternatives to wiki-compiler
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceProvides a lightweight personal knowledge base MCP server that compiles raw materials into interconnected Wiki pages, with hybrid search (BM25, optional vector, link expansion) and tools for querying, reading, writing, and ingesting content.5-
- AlicenseNot gradedqualityCmaintenanceMCP server for persistent, compounding markdown wikis maintained by LLMs. Enables incremental knowledge base building with interlinked pages, search, and raw source management.24 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables building and querying a local wiki knowledge base from raw source files via MCP tools and a PyQt viewer.-

Shreg compilerofficial
FlicenseNot gradedqualityBmaintenanceCompiles an Obsidian knowledge graph into a queryable MCP server, allowing AI agents to search concepts, get nodes, and retrieve related information.-- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to fetch webpages, convert them to Markdown, index into SQLite FTS5, and query the knowledge base through MCP tools.-
- AlicenseNot gradedqualityBmaintenanceMCP server for browsing Obsidian-compatible Markdown vaults, searching notes, viewing backlinks and knowledge graphs, and adding selected content to chat context.13 npmMIT
TDQS
Scored across 3 tools
Each tool targets a distinct operation: adding documents, searching the wiki, and auditing it. There is no overlap in purpose, and the descriptions clearly differentiate ingestion, query, and maintenance tasks.
All tool names follow a consistent verb_noun pattern: add_document, search_wiki, lint_wiki. This makes the set predictable and easy to navigate.
With only 3 tools, the server is at the low end of the typical range. The tools are focused and each serves a clear purpose, but the set is slightly sparse for a wiki compiler.
The core operations of adding, searching, and linting are covered, but there are no update, delete, or list document tools. This creates notable gaps in the document lifecycle and forces agents to work around them.