MCP server that exposes an Obsidian markdown vault (wiki with YAML frontmatter + wikilinks) as tools for an LLM agent.
Strong tool coverage (27 tools) with consistent naming (verb_noun pattern: get_, add_, archive_, resolve_, search_, create_, move_, check_, register_, index_, run_, prune_). Descriptions are detailed and context-rich, averaging 150-250 chars, well above the 34-char baseline minimum. All tools have explicit input schemas with type definitions. However, output schemas are not formally documented, responses are described in prose but lack structured JSON Schema definitions. Error handling is implicit (tools 'refuse to act' or 'fail if') but lacks explicit recovery guidance. Security considerations (write vs read-only risk labels) are present but not formalized as tool annotations. Composition is excellent: tools chain naturally (e.g., search_wiki → get_page → get_backlinks), and parameters accept human-friendly identifiers (marker as substring, name as wikilink).
Append a raw, uncategorized idea/thought to today's daily note ('## 📥 Capture bruta') -- baja fricción de captura (22/8/2026): no hace falta decidir sección/categoría al momento de escribir, eso lo resuelve INGERIR después. Destino natural para mensajes de voz/texto sueltos por Telegram -- si el usuario tira una idea suelta sin pedir nada puntual, colgarla acá en vez de perderla. A diferencia de add_tarea_diaria, APPENDEA al final (log cronológico, no cola de tareas). Fails if today's note doesn't exist yet or has no '## 📥 Capture bruta' section.
Add a new open item to hot.md's 'Decisiones pendientes' section -- counterpart to archive_pendiente, which only removes/relocates an item that already exists. Use this whenever the user asks to note, remember, or track something new as a pendiente (there was previously no way to create one via MCP, only to archive an existing one — a real gap found in Hermes' Telegram usage). If `texto` doesn't already include a dd/mm/yyyy date, today's date is appended automatically so it doesn't show up as stale/undated right away. Dedup check (added 1/8/2026): before writing, compares `texto` against every open item already in the section. If a near-duplicate exists, the write is skipped and the existing item's text is returned instead — set force=True to add anyway if it's genuinely a different item.
Add a new open task to today's daily note ('## ✅ Tareas'), instead of hot.md. Counterpart to add_pendiente for items with a ~1-day execution horizon (convención adoptada 29/7/2026): use this for something actionable today/this week, use add_pendiente for an open-ended decision without a concrete action date. Fails if today's note doesn't exist yet or has no '## ✅ Tareas' section.
Output schemas not formally documented. Tool descriptions state what is returned in prose ('Return the full contents...', 'Returns a report') but lack JSON Schema definitions. LLMs cannot reliably parse unstructured text responses or plan downstream tool calls without knowing field names and types.
Error handling lacks explicit recovery guidance. Tools 'refuse to act if' or 'fail if' conditions are met, but error responses do not include actionable next steps (e.g., 'Try search_wiki() with a partial name'). Agents cannot self-correct without explicit guidance.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2026-07-28+ | v2 |
Move one open (not yet resolved) item out of hot.md's 'Decisiones pendientes' into wiki/pendientes-archivo.md, where it stays real, searchable knowledge (indexable by search_semantic) without weighing down every get_pendientes() call. `marker` must be a unique substring of the item's text — refuses to act if it matches zero or several items.
Chequea TODO el rango de días de una sola pasada por solapamientos entre eventos recurrentes/únicos de Calendario/, en vez de descubrirlos uno a la vez cuando ya chocaron. Solo reporta, no modifica nada.
Cap de hot.md 'Antigüedad máxima de inbox/captura' (20 días) -- reporta archivos de _Inbox/ más viejos que max_dias por mtime, para dejar de tener ese cap declarado sin ningún mecanismo de medición real. Solo reporta, no modifica ni mueve nada.
Check which _Inbox/ files (paths relative to _Inbox/) were already evaluated in a previous INGERIR run, by content hash — not filename. Call once for the whole batch, before reading any file, at the start of INGERIR. Replaces the manual grep of wiki/log.md for prior verdicts; covers every verdict (pasa/descartado/fragmento_extraido/link_con_anotacion), not just discards.
Create a new wiki page (fuente/entidad/concepto/sintesis), enforcing the required frontmatter fields for that type. Refuses to overwrite.
Server health check: verify the vault root is set, all required directories exist, the FTS5 and semantic indices are reachable, and the MCP server itself is responsive. Returns a report.
Return every wiki page that links to [[name]] via wikilink — the reverse of get_page's forward resolution ('what links here').
Return the full contents of wiki/hot.md — the vault's active context.
Return the full contents of wiki/index.md — the vault's master index.
Eventos del calendario local (Calendario/, Full Calendar Remastered) para una fecha (YYYY-MM-DD, default hoy) y rango de días. 100% local, no usa Google Calendar.
Resolve a [[wikilink]] name (e.g. 'ivan-ledesma') to its file contents.
Return the 'Decisiones pendientes' section of wiki/hot.md, budgeted to ~28K chars and ranked by most-recent-date-mentioned — a short, focused slice for callers with a small context budget (e.g. the Hermes heartbeat), where get_hot()'s full ~100K chars gets truncated before reaching this section. Older items past the budget are listed by title only, with a pointer to search_semantic and pendientes-archivo.md.
Return wiki/hot.md's 'Cuellos de botella activos' section — the short, canonical list of active blockers. Call this before answering any synthesis question about priorities/bottlenecks/status instead of answering from conversational memory alone.
Rank every other wiki page by weighted relevance to [[name]] (direct link, co-citation by a shared fuente, Adamic-Adar over common neighbors, same-type bonus) and return the top N. A heuristic for surfacing cluster/síntesis candidates beyond exact tag/entity matches — not exact like get_backlinks, always eyeball the result.
Walk every wiki/**/*.md page and (re)index it into the semantic and FTS5 collections. Incremental: compares each page's content hash against what's stored, only re-indexes new/changed pages, deletes pages that no longer exist in the vault.
Move a file from _Inbox/ to its PARA destination (step 9 of INGERIR). target_folder must be relative to the vault root and rooted at one of Notas/Areas/Proyectos/Archivo/Recursos. Refuses to overwrite an existing file at the destination.
Compact wiki/hot.md's '### Brechas documentadas' section (under '## Fallas abiertas y pendientes'): bullets marked '**cerrado/resuelto (DD/MM/YYYY)**' whose date has a matching '## YYYY-MM-DD' section in log.md, and that don't also mention an unresolved 'pendiente' elsewhere in the bullet, get collapsed to a 1-line stub pointing at log.md. Everything else is left untouched and reported separately. Returns the report; only writes to hot.md when dry_run=False.
Compact wiki/hot.md's 'Última sesión' section: entries older than 3 days with a log.md pointer get collapsed to a 1-line stub (already preserved there in full). Entries within 3 days, or without a log.md pointer, are left untouched. Returns the report; only writes to hot.md when dry_run=False.
Record the final INGERIR verdict for one _Inbox/ file in the manifest, keyed by content hash. veredicto must be one of: pasa, descartado, fragmento_extraido, link_con_anotacion.
Mark one 'Decisiones pendientes' item as resolved and move it to wiki/log.md — counterpart to archive_pendiente (which is for items that are still open but stale, not finished). Use this when the user says a pendiente is actually done. `marker` must be a unique substring of the item's text — refuses to act if it matches zero or several items.
Lint the entire vault: check every page for frontmatter completeness, wikilink resolution, backlink presence, and other structural invariants. Returns a report; only writes when dry_run=False (for auto-fixes like adding missing backlinks).
Semantic search: find the pages whose meaning is closest to `query`.
Full-text search across every wiki/**/*.md file, ranked by BM25 relevance (SQLite FTS5).
Post-operation verification for one wiki page (the pstack-style "control CLI", scoped to a single page instead of the whole vault — that's run_lint's job — or server plumbing — that's doctor's job). Checks it exists in exactly one subfolder, frontmatter is valid and complete for its type, every [[wikilink]] in its body resolves, and it has at least one incoming backlink. Call right after create_page to get real evidence the page landed well-formed, not just that no exception was raised.
Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are not declared in FastMCP schema. Risk labels (READ_ONLY, WRITE) are present in documentation but not exposed to the MCP protocol, limiting client-side safety checks and UI hints.
Pagination not implemented for list-like tools. search_wiki accepts max_results (default 20) and get_related_pages accepts top_n (default 8), but neither returns a total count, next_cursor, or offset for continuation. Large result sets risk context window exhaustion.
Dry-run parameters default to true (prune_hot, prune_brechas, index_vault, run_lint), which is safe but may confuse agents expecting immediate side effects. Descriptions should explicitly state 'no changes are written unless dry_run=False' to prevent agent confusion.