LLM Wiki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLM_WIKI_DIR | No | Ruta al directorio donde se almacenan los archivos Markdown de la wiki. | |
| MCP_PROJECT_ID | Yes | Identificador del proyecto para aislar el conocimiento. | |
| OLLAMA_EMBED_DIMS | No | Dimensiones del modelo de embeddings. | 768 |
| OLLAMA_EMBED_MODEL | No | Modelo de embeddings de Ollama. | nomic-embed-text |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_noteA | Ingesta una nota con embeddings. Extrae metadata YAML, asigna project_id e is_global, segmenta el texto, genera embeddings (con timeout) y persiste atómicamente. |
| search_wikiA | Busca contexto usando búsqueda semántica híbrida (KNN Vec0 + FTS5) fusionada mediante RRF. Explicación: Si Ollama está disponible, ejecuta tanto búsqueda semántica como léxica, filtrando por proyecto y fusionando resultados usando Reciprocal Rank Fusion (RRF). Si Ollama no está disponible o falla, degrada a búsqueda léxica únicamente. |
| get_ingestion_statusC | Reporta notas que hayan fallado o hayan sido omitidas (SKIPPED). Opcionalmente filtra por status. |
| list_notesC | Lista las notas almacenadas, con filtros opcionales. |
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 4 tools
Each tool has a distinct purpose: ingestion status, listing notes, saving a note, and searching the wiki. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (get_ingestion_status, list_notes, save_note, search_wiki), making them predictable.
With 4 tools, the server is well-scoped for a wiki MCP server, covering essential operations without being too sparse or overloaded.
The set covers core operations (save, list, search, status). Missing a delete or explicit get single note, but list_notes with filters can likely retrieve one, so only a minor gap.