MCP server for Obsidian vaults — Dataview, Tasks, Templater, Excalidraw, Omnisearch
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"obsidian-mcp-jayfraggs","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Obsidian MCP A production-grade [Model Context Protocol](https://modelcontextprotocol.io) server that connects Claude Desktop (and any compatible LLM) directly to your Obsidian vault. Supports **Dataview · Tasks · Templater · Excalidraw · Omnisearch** — generating plugin-native markdown that Obsidian can read and render without any extra configuration. --- ## Table of contents 1. [Requirements](#requirements) 2. [Installation](#installation) 3. [Configuration](#configuration) 4. [Connect to Claude Desktop](#connect-to-claude-desktop) 5. [Connect to other LLMs](#connect-to-other-llms) 6. [Web UI](#web-ui) 7. [Obsidian Local REST API plugin (optional)](#obsidian-local-rest-api-plugin) 8. [AI Rules system](#ai-rules-system) 9. [Plugin reference](#plugin-reference) 10. [Vault adapter modes](#vault-adapter-modes) 11. [Permission profiles](#permission-profiles) 12. [Troubleshooting](#troubleshooting) 13. [Developer docs](#developer-docs) --- ## Requirements | Tool | Minimum version | |------|----------------| | Python | **3.11** | | uv (recommended) or pip | any recent | | Obsidian | any version (vault is plain markdown) | | Claude Desktop | any current release | --- ## Installation ### Option A — uv (recommended) ```bash # 1. Clone the repository git clone https://github.com/your-org/obsidian-mcp.git cd obsidian-mcp # 2. Create a virtual environment and install uv venv uv pip install -e ".[dev]" # 3. Copy and edit the environment file cp .env.example .env ``` ### Option B — pip ```bash git clone https://github.com/your-org/obsidian-mcp.git cd obsidian-mcp python -m venv .venv source .venv/bin/activate # Windows: .venv\Scripts\activate pip install -e ".[dev]" cp .env.example .env ``` --- ## Configuration Edit `.env` in the project root: ```env # ── Required ──────────────────────────────────────────────────────── OBSIDIAN_MCP_VAULT_PATH=/absolute/path/to/your/ObsidianVault # ── Optional: server identity ──────────────────────────────────────…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.