obsidian-rag
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_RAG_DB | Yes | Absolute path to the persistent Chroma directory | |
| OBSIDIAN_RAG_MODEL | No | Ollama embedding model | all-minilm:22m |
| OBSIDIAN_RAG_VAULT | Yes | Absolute path to the Obsidian vault | |
| OBSIDIAN_RAG_COLLECTION | No | Chroma collection name | obsidian_notes |
| OBSIDIAN_RAG_OLLAMA_HOST | No | Ollama server address | http://localhost:11434 |
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 |
|---|---|
| search_notesB | Semantically search indexed Obsidian notes and return cited passages. |
| read_noteA | Read one Markdown note or an exact heading using a safe relative path. |
| vault_statusA | Check local index availability, chunk count, and refresh state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ask_obsidian | Answer a question using the Obsidian vault with explicit citations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: semantic search, direct note reading, and vault/index status. There is no overlap or ambiguity between them.
search_notes and read_note follow a clear verb_noun pattern, but vault_status is a noun phrase rather than get_vault_status or check_vault_status. This is a minor deviation from an otherwise consistent snake_case convention.
Three tools is appropriate for a focused RAG server covering search, retrieval, and system status. No tool feels redundant or missing enough to bloat the surface.
The core read/search/status workflow is well covered for a read-only Obsidian RAG server. A possible minor gap is the lack of an explicit refresh/reindex action, though the status tool reports refresh state.