obsidian-rag-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAG_TOP_K | No | Retrieved chunks per question (1–20) | 4 |
| RAG_BASE_URL | No | LM Studio server URL | http://localhost:1234/v1 |
| RAG_DOCS_DIR | Yes | Vault / notes directory | |
| RAG_CHAT_MODEL | No | Chat model id (auto-detected if not set) | |
| RAG_EMBED_MODEL | No | Embedding model id (auto-detected if not set) |
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_notesA | Search the user's markdown notes for passages relevant to the query. Use this for any question about the user's notes, then answer using only the returned passages and cite their source filenames. Args: query: A natural-language question or topic to search for. top_k: How many passages to return (default 4, max 20). |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clear and distinct.
The tool name 'search_notes' follows a clear verb_noun pattern. As the only tool, it is internally consistent.
A single tool is borderline. It is not trivial and serves the core purpose of searching notes, but the tool surface feels thin for a server intended to support RAG over an entire note collection.
The search tool covers the primary retrieval need. Minor gaps exist, such as no ability to list all notes or fetch a specific note directly, but these can be worked around by searching with broad queries.