Obsidian Lumina MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_PATH | No | Path to the LanceDB database (relative or absolute) | ./.lancedb |
| EMBED_MODEL | No | The Ollama embedding model to use | bge-m3:latest |
| OBSIDIAN_PATH | Yes | Absolute path to the Obsidian vault folder |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesB | Search Obsidian notes using vector similarity search |
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 overlap or confusion. The tool's purpose is clearly defined as searching notes via vector similarity.
A single tool named 'search_notes' follows a clear verb_noun pattern in snake_case. There are no other tools to create inconsistency.
A single tool is too few for a server named 'Obsidian Lumina MCP', which implies broader note management capabilities. The tool surface feels extremely thin.
The server only supports searching notes, missing essential operations like retrieving, creating, updating, or deleting notes. Agents would face significant gaps when attempting to work with Obsidian content.