llm-wiki-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_wikiC | Initialize a minimal Karpathy-style LLM Wiki structure without overwriting by default. |
| inspect_wikiC | Inspect whether a directory has the minimal llm-wiki structure. |
| search_wikiC | Search llm-wiki formal pages and/or raw sources with wiki metadata. |
| read_pageC | Read a formal llm-wiki page and return wiki metadata. |
| read_raw_sourceC | Read an evidence-preserving raw source under raw/. |
| create_raw_sourceA | Create a new raw source under raw/. Existing files are never overwritten. |
| append_logB | Append a structured entry to log.md and trim old entries to retention. |
| compile_pageC | Compile a raw source into a persisted formal page Candidate. |
| create_update_candidateC | Generate a persisted update Candidate for an existing formal page. |
| apply_candidateC | Apply an approved Candidate bundle atomically. |
| run_lintC | Run wiki lint and return structured lint results. |
| knowledge_health_reviewC | Summarize wiki health across lint, sources, duplicates, stale pages, and confidence. |
| write_public_draftC | Render a public-site markdown draft candidate without publishing it. |
| validate_public_safetyC | Validate public-site candidate content for sensitive material. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a distinct action in the wiki lifecycle (init, inspect, read, write, compile, apply, lint, search, log, health review, validate, draft). There is no overlap or ambiguity between tool purposes.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_raw_source, apply_candidate, knowledge_health_review). No mixing of conventions or vague verbs.
14 tools is well-scoped for a wiki management server. The number covers all necessary operations without being excessive or insufficient.
The tool set covers the full lifecycle from initialization to inspection, raw source management, candidate compilation and application, linting, health review, search, logging, and public draft writing. No obvious gaps for the intended domain.