An MCP server exposing tools to interact with an Obsidian vault.
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":"iflow-mcp-obsidian-mcp","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 Tool Server [](https://github.com/rivassec/obsidian-mcp/actions/workflows/trivy-scan.yml) [](https://bandit.readthedocs.io) [](https://github.com/aquasecurity/trivy) This project provides a Model Context Protocol (MCP) server that exposes tools for interacting with an Obsidian vault. ## Table of Contents - [Features](#features) - [Installation](#installation) - [Configuration](#configuration) - [Running Manually (for Testing/Debugging)](#running-manually-for-testingdebugging) - [Client Configuration (Example: Claude Desktop)](#client-configuration-example-claude-desktop) - [Available MCP Tools](#available-mcp-tools) - [Roadmap](#roadmap) - [Frequently Asked Questions (FAQ)](#frequently-asked-questions-faq) - [Contributions Welcome!](#contributions-welcome) ## Features Allows MCP clients (like AI assistants) to: - Read and write notes - Manage note metadata (frontmatter) - List notes and folders - Search notes by content or metadata - Manage daily notes - Get outgoing links, backlinks, and tags ## Installation 1. **Clone the repository** (if you haven't already): ```bash # git clone <repository-url> # cd OMCP ``` 2. **Navigate to the project directory**: ```bash cd /path/to/your/OMCP ``` 3. **Create a Python virtual environment** (recommended to avoid dependency conflicts): ```bash python -m venv .venv ``` 4. **Activate the virtual environment**: * On Windows PowerShell: ```powershell .venv\Scripts\Activate.ps1 ``` * On Linux/macOS: ```bash source .venv/bin/activate ``` (Your terminal prompt should …
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.