obsidian_mcp
Provides tools for managing notes in an Obsidian vault, including listing, reading, searching, creating, appending, updating notes, and managing wikilinks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@obsidian_mcpsearch my notes for AI research papers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Obsidian MCP Server
Have been using obsidian for quite awhile (have years and years of notes in my vault) and thought we could benefit from some kind of MCP server.
This can be used to read notes from your vault, have AI agents create notes, etc.
Will periodically add more tools and enhancements to this...
Note: This is meant to be used locally or hosted yourself for now. This MCP server currently does not come with an AKS deployment or anything like that. Your vault should ideally also be local (unless you're using some weird plugin), so don't see this as a serious downside.
Setup
Install dependencies
Requires uv. Clone the repo, then:
# Install runtime dependencies
uv sync -p $(cat ./.python-version)
# Install with test extras
uv sync --extra test
# Install with dev extras
uv sync --extra dev
# Run tests
uv run pytest
# Run the server directly
uv run python -m obsidian_mcp.mainThe virtual environment is created automatically by uv inside .venv/. Use .venv/bin/python as the interpreter path in your MCP client config.
MCP client config
{
"mcpServers":{
"obsidian_mcp":{
"command":"/<path_to_project>/.venv/bin/python",
"args": ["-m", "obsidian_mcp.main"],
"env":{
"OBSIDIAN_VAULT__PATH": "<local vault path>",
"OBSIDIAN_VAULT__ATTACHMENT_PATH": "<path to attachments folder>",
"OBSIDIAN_LOGGING__LEVEL": "INFO",
"OBSIDIAN_LOGGING__FORMAT": "%(asctime)s | %(levelname)-8s | %(name)s | %(message)s",
"OBSIDIAN_SERVER__HOST": "127.0.0.1",
"OBSIDIAN_SERVER__PORT": 8000,
"OBSIDIAN_VAULT__ENABLE_WIKILINKS": "True",
"OBSIDIAN_VAULT__ENABLE_FRONTMATTER": "True",
"OBSIDIAN_SEARCH__ENABLED": "True",
"OBSIDIAN_SEARCH__MAX_RESULTS": 100
}
}
}
}Note: If you have <project_dir>/.env file populated. You can remove these entries in the mcp config. The config class should load the
.env.
Related MCP server: obsidian-mcp
Tools
Notes
Tool | Description |
| List all notes in the vault or a subdirectory. Optionally exclude |
| Read a note by its vault-relative path. Returns path, title, tags, frontmatter, and body. |
| Search notes for a literal query string. Supports case sensitivity, frontmatter inclusion, and excluding |
| Create a new note at a given vault-relative path with optional YAML frontmatter. |
| Append text to the end of an existing note without overwriting it. |
| Overwrite the body of an existing note, optionally replacing its frontmatter. |
| Merge-patch specific frontmatter keys without rewriting the note body. Set a key to |
| Delete a note by moving it to |
| Move or rename a note and update all vault wikilinks that reference it. |
Graph & Links
Tool | Description |
| Return all outgoing wikilink targets from a note's body. |
| Return all notes in the vault that contain a wikilink pointing to the given note. |
| Return the full vault link graph as nodes and edges. Scoped to a subdirectory when |
| Scan the vault for wikilinks that point to non-existent notes. |
| Return all notes that have no incoming wikilinks from other notes. |
Tags & Metadata
Tool | Description |
| List all unique tags across the vault. Optionally include per-tag note counts. |
| Return all notes that contain a given tag (frontmatter or inline). |
| Return notes matching any (or all) of a list of tags. |
Vault
Tool | Description |
| Return a snapshot of vault-level statistics: note count, folder count, unique tags, broken links, orphans, and attachment counts (when attachment path is configured). |
| List all subdirectory paths within the vault or a given sub-path. |
Attachments
Requires
OBSIDIAN_VAULT__ATTACHMENT_PATHto be set in your MCP config.
Tool | Description |
| List all attachment files under the attachment root or a subdirectory. Returns path, name, suffix, and size for each file. |
| Return metadata for a single attachment file by its path relative to the attachment root. |
| Return all attachments not referenced by any note in the vault (checks both wikilinks and markdown links). |
Prompts
Prompt | Description |
| Fetches a note by path and returns a structured prompt asking the LLM for a TL;DR, key-point bullets, and any action items or decisions. |
| Given a list of unused attachment paths, returns a prompt guiding the LLM to help decide which files to keep or delete. |
This server cannot be deployed
Maintenance
Related MCP Connectors
Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.
Shared long-term memory vault for AI agents with 20 MCP tools.
MCP-native notes and memory for ChatGPT, Claude, and other AI tools.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceTurns your Obsidian vault into an MCP-enabled workspace with tools for reading/writing notes, managing folders, running semantic searches, and maintaining long-term memory—all while keeping data local to your vault.148,515 npm153MIT
- AlicenseBqualityBmaintenanceBridges Obsidian vaults with MCP-compatible AI tools, enabling read/write/search of notes, task management, and vault operations through 34 tools and prompt templates.3458 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to remotely access and interact with Obsidian vaults via MCP, supporting note operations, tag management, graph queries, and command execution.4GPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to search, read, and write notes in an Obsidian vault via MCP tools, and monitor product handoffs and state.MIT