Best for
- Research material that benefits from review, provenance, and reuse
- Codebase documentation, team handbooks, standards, design notes, and decision logs
- Agent workflows that precompile knowledge before querying it
L
llmwiki MCP Server
Community
Compile raw sources into an auditable, interlinked knowledge base.
GitHub source repository ↗
57FMRS · C
The source identifies an MCP server and two explicitly named MCP tools, get_context_pack and run_eval, but does not specify transport details, client compatibility, or client installation configuration. The project is MIT-licensed and uses the repository root as its server path. Its primary purpose is compiling source material into reviewable, citation-aware, searchable knowledge.
llmwiki is a knowledge compiler that turns papers, notes, READMEs, transcripts, PDFs, images, or web pages into an interlinked Markdown wiki with citations, metadata, review state, and provenance. Its MCP server lets compatible agents ingest, compile, query, read, lint, evaluate, inspect status, build context packs, and exchange Open Knowledge Format bundles. The server path is the repository root.
Tools
get_context_pack
Builds a citation-aware evidence context pack for an agent.
run_eval
Runs knowledge-base quality evaluation; the fast suite needs no provider, while the full suite's citation-support judging requires one.
Setup
Node.js 24 or newer is required. Install with npm install -g llm-wiki-compiler, then run llmwiki serve --root <project-directory> from the knowledge-base project.
Fit and risk
Not for
- High-churn log streams where raw search is sufficient
- General-purpose static-site generation
- Heavy ontology databases
Required permissions
- Access to the selected knowledge-base project and its sources, wiki, and .llmwiki data
- Appropriate network access when ingesting web pages or using external connectors; the README does not specify connector permissions
- Provider credentials at call time for LLM-backed operations
Risks and side effects
- LLM-generated content may contain confidence, contradiction, provenance, or freshness issues
- External OKF imports enter the review queue by default, but explicitly trusted imports can write to the active knowledge base
- Ingest, connector, import, and other write operations can change project data; review, lint, and eval should be used
- The README does not specify an MCP transport or client configuration, so client compatibility cannot be assumed
Troubleshooting
- Verify that Node.js is version 24 or newer
- Verify that --root points to the knowledge-base project directory
- Run llmwiki status, llmwiki lint, and llmwiki eval to inspect state and quality
- If an LLM-backed operation fails, check the selected provider and its credentials
- For stale pages, run llmwiki refresh --stale --dry-run before applying repairs
Use cases
Compile raw material into a persistent interlinked Markdown wiki
Build citation-aware evidence packs for agents
Check citations, links, stale pages, and knowledge quality
Query, read, and exchange compiled knowledge through MCP
Supported clients
Supported clients have not been confirmed yet.