mcp-markdown-vault
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (SSE mode only) | 3000 |
| OLLAMA_URL | No | Set to enable Ollama embeddings | |
| VAULT_PATH | No | Markdown vault directory | /vault |
| OLLAMA_MODEL | No | Ollama embedding model name | nomic-embed-text |
| OLLAMA_DIMENSIONS | No | Ollama embedding vector dimensions | 768 |
| MCP_TRANSPORT_TYPE | No | Transport mode: 'stdio' (single client) or 'sse' (multi-client HTTP) | stdio |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vaultB | Manage vault notes. Vault scope: general markdown notes vault. Actions: list (browse notes), read (full note), create/update/delete (whole-file writes), stat (metadata), create_from_template (scaffold from template). For search strategy and conventions, read vault://overview. |
| editA | Edit notes safely. Vault scope: general markdown notes vault. Supports AST edits by heading/block ID, freeform line/string replacement, frontmatter_set metadata merges, batch operations (max 50), and dryRun=true unified diff previews. Read vault://overview for editing strategy and conventions. |
| viewB | Read and search markdown notes. Vault scope: general markdown notes vault. Actions: search (heading-aware fragment retrieval with TF-IDF + proximity), semantic_search (vector + lexical hybrid for conceptual queries), global_search (cross-vault exact-match grep), outline (file or directory structure tree), read (full file or single section by heading), frontmatter_get (parse YAML frontmatter), bulk_read (read multiple files/headings in one call), backlinks (find all notes linking to a given path). |
| workflowC | Manage optional agent workflow state for this vault (general markdown notes vault): status, transition, history, reset. Typical flow: search → open_note → save → done; read vault://overview for usage guidance. |
| systemA | System administration for this vault (general markdown notes vault). Actions: status (indexing/backlinks/workflow health), reindex (async rebuild), overview (folder tree), overview_status (meta/overview.md state), prepare_overview (gather evidence), save_overview (persist host-written overview). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| rebuild-overview | Guides the host LLM through the assisted overview flow: gather evidence, generate prose, save, and verify. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| vault-overview | Complete vault context: live stats, overview, and conventions (frontmatter schema, tags, naming). |
| vault-stats | Live vault statistics as JSON. |
TDQS
Scored across 5 tools
Tools have distinct purposes overall, but there is some overlap between 'edit' and 'vault' (both modify notes) and between 'vault' and 'view' (both read notes). Descriptions help clarify boundaries, but slight ambiguity remains.
Tool names are single words and lowercase, but they do not follow a consistent verb_noun pattern. Names like 'edit', 'system', 'vault', 'view', 'workflow' are more categorical than action-oriented, deviating from common MCP naming conventions.
With 5 tools, the server is well-scoped for a markdown vault. Each tool covers a distinct area (editing, administration, CRUD, reading/searching, workflow), and none seem extraneous.
The tool set covers CRUD operations, advanced editing, searching, system management, and workflow state. Minor gaps like renaming or moving notes exist, but core functionality is solidly addressed.