obsidian-mcp-server
Health Warn
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Pass
- Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
- Permissions — No dangerous permissions requested
No AI report is available for this listing yet.
MCP server that connects AI assistants to your Obsidian vault. Read, search, and manage notes through the Model Context Protocol.
Obsidian MCP Server
An MCP (Model Context Protocol) server that makes an Obsidian vault useful to AI clients such as Claude Desktop, Claude Code, Cursor, and Cline. It is designed as a public, reusable core with optional tool sets and vault-specific profiles layered on top.
Features
Public Core
The core tool set is always available and stays vault-agnostic:
- Vault diagnostics, task routing, and MCP client root inspection.
- Note listing, reading, metadata inspection, and search.
- Vault context resources for profiles, skills, standards, and local docs.
- Core prompts for structured notes, template usage, and context exploration.
Optional Tool Sets
Optional packs are enabled explicitly from .agents/vault.yaml orOBSIDIAN_MCP_TOOL_SETS:
notes_write: Create, patch, move, and delete notes.vault_analysis: Vault statistics, tags, links, backlinks, and graph tools.agents_admin: Skill creation, validation, and cache management.youtube: Transcript extraction.obsidianrag: Semantic search through the external ObsidianRAG service.canvas/kanvas: Canvas and workflow helpers.- Profile packs: Personal workflows only when a vault profile opts in.
Design Principles
- Public core, personal profiles: The repository remains reusable; local workflows live in vault configuration and resources.
- English technical surface: Tool names, prompt names, docs, and code identifiers are English.
- Safe by default: Write tools are opt-in, protected paths are blocked, and large reads are capped.
- External RAG by integration: Advanced semantic search delegates to ObsidianRAG instead of duplicating a RAG stack inside the MCP server.
Quick Setup
Prerequisites
- Python 3.11+
- uv (Recommended)
Steps
Clone:
git clone https://github.com/Vasallo94/obsidian-mcp-server.git cd obsidian-mcp-serverInstall:
make install # Optional legacy in-process semantic stack: pip install "obsidian-mcp-server[rag]"Configure:
cp .env.example .env # Edit .env with the absolute path to your Obsidian vault
Usage
The MCP server connects to compatible clients using the uv run obsidian-mcp-server command. Below are setup instructions for popular AI clients.
Claude Desktop Integration
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"obsidian": {
"command": "uv",
"args": ["run", "obsidian-mcp-server"],
"env": {
"OBSIDIAN_VAULT_PATH": "/Absolute/Path/To/Your/Vault"
}
}
}
}
Optional Tool Sets
Enable optional tools from the client environment:
{
"env": {
"OBSIDIAN_VAULT_PATH": "/Absolute/Path/To/Your/Vault",
"OBSIDIAN_MCP_TOOL_SETS": "notes_write,vault_analysis,obsidianrag"
}
}
Or declare them in your vault profile:
profile:
name: "my_profile"
prompt_sets:
- "mermaid"
tool_sets:
- "notes_write"
- "vault_analysis"
standards:
media: "Standards/Media.md"
local_docs:
index: "README.md"
ObsidianRAG Integration
For semantic vault search, enable the obsidianrag tool set and declare the
integration:
profile:
tool_sets:
- "obsidianrag"
integrations:
obsidianrag:
project_path: "/path/to/ObsidianRAG"
api_url: "http://127.0.0.1:8000"
env:
OBSIDIANRAG_LLM_MODEL: "gemma3"
OBSIDIANRAG_OLLAMA_EMBEDDING_MODEL: "embeddinggemma"
Then read obsidian://integrations/obsidianrag/setup or callrag.setup_status. Agents should show setup commands before installing
dependencies, starting services, pulling models, or rebuilding the index.
Cursor & Cline Integration
For other clients like Cursor or Cline, you can add it as a new MCP server in their settings panel by specifying:
- Type:
command - Command:
uv run obsidian-mcp-server - Ensure the
OBSIDIAN_VAULT_PATHenvironment variable is available to the instance running the command.
Technical Documentation
To dive deeper into how the server works and how to customize it, check our detailed guides located in the docs/ folder:
- Architecture: Modular structure and data flow of the project.
- Tool Reference: Complete list of available MCP tools and their parameters.
- Server Configuration: Guide on environment variables and technical configuration.
- Agent Setup: How to organize your vault (
.agents/) with skills and contextual rules. - Semantic Search: ObsidianRAG integration and legacy RAG migration notes.
- Agent Feedback: How agents can report MCP friction with AFP out-of-band.
- Future Roadmap: Planned improvements and next steps for the server.
Development & Quality
| Command | Description |
|---|---|
make test |
Run the test suite (pytest) |
make lint |
Run static checks (Ruff + Mypy + Pylint) |
make format |
Automatically format code |
make dev |
Run the MCP inspector for live testing |
License
This project is licensed under the MIT License.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found