obsidian-mcp-context
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 |
|---|---|
| list_vault_notesC | List text notes found in the configured vault. |
| search_vault_blocksB | Search parsed note blocks with file and line provenance. |
| list_vault_tasksC | List parsed Markdown tasks with provenance. |
| get_vault_note_contextA | Fetch all parsed context for one vault-relative note path. |
| get_vault_warehouse_summaryC | Summarize deterministic warehouse dimensions, facts, and marts. |
| list_vault_entitiesC | List modeled entities derived from notes, wikilinks, and tags. |
| list_vault_entity_typesC | List entity types observed in the dbt entity registry. |
| get_vault_entity_timelineC | Return timeline rows connected to a modeled entity. |
| get_vault_entity_contextB | Return generic dbt mart-backed context for any typed entity. |
| list_vault_entity_eventsB | List generic entity events from the dbt warehouse. |
| list_vault_entity_relationshipsC | List generic relationships between modeled entities. |
| list_vault_entity_statesC | List generic state rows for stateful entities. |
| list_vault_entity_open_loopsC | List open loops attached to any modeled entity type. |
| search_vault_agent_contextC | Search curated deterministic context rows for agent use. |
| get_vault_project_contextB | Return dbt mart-backed project context, including decisions, risks, and open loops. |
| get_vault_person_contextB | Return dbt mart-backed person context, including decisions, risks, and open loops. |
| list_vault_open_loopsC | List dbt mart-backed open loops from unchecked tasks. |
| list_vault_decisionsC | List dbt mart-backed decisions with optional entity and status filters. |
| list_vault_risksB | List dbt mart-backed risks with optional entity and status filters. |
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 19 tools
Each tool targets a specific aspect of the vault context: get operations for different entity types (entity, note, person, project), list operations for distinct entity attributes (decisions, risks, open loops, tasks, etc.), and search operations. There is no meaningful overlap; every tool has a clearly distinct purpose.
All tools follow a consistent verb_vault_noun pattern with snake_case (e.g., get_vault_entity_context, list_vault_entities, search_vault_blocks). The use of 'vault' as a prefix is uniform, and the verbs are limited to get, list, and search. Minor singular/plural variations (entity vs. entities) do not disrupt the predictable structure.
With 19 tools, the server is slightly above the typical well-scoped range (3-15) but still reasonable given the breadth of entity types and operations. Each tool seems justified for the domain of vault context retrieval, so the count is appropriate.
The tool set covers a wide range of read operations: getting specific entity contexts, listing various entity attributes and events, and searching. Minor gaps exist, such as the absence of get operations for individual decisions, risks, or tasks (only list is available). However, agents can still retrieve needed information through filtering, so the surface is nearly complete for a read-only context server.