Obsidian MCP server

Connect Obsidian

{"mcpServers": {"mcp-obsidian": {"command": "uvx", "args": ["mcp-obsidian"], "env": {"OBSIDIAN_API_KEY": "<YOUR_OBSIDIAN_API_KEY>", "OBSIDIAN_HOST": "<your_obsidian_host>", "OBSIDIAN_PORT": "<your_obsidian_port>"}}}}

docker compose run --rm -T mcp-obsidian

Copy the API key from the Local REST API plugin settings in Obsidian. Host defaults to 127.0.0.1 and port to 27124 when not set. The README only documents Claude Desktop, but the same JSON block works in any client that runs local stdio servers; if a client cannot find uvx, put the full path from `which uvx` in the command.

What the Obsidian MCP server does

mcp-obsidian is a community MCP server, written in Python by Markus Pfundstein, that lets an AI agent work inside an Obsidian vault. It does not open the vault files directly: it calls the Local REST API community plugin, which runs inside the Obsidian app on your machine and listens on port 27124 by default. The agent can list folders, read a note, run a text search across the whole vault, and write back.

The mcp-obsidian write tools cover three cases. append_content adds text to a new or existing note, patch_content inserts text next to a heading, a block reference or a frontmatter field, and delete_file removes a file or folder. That is enough for jobs like turning meeting notes into a summary note or adding a task under a heading, without the agent rewriting whole files.

mcp-obsidian runs locally with uvx or in Docker, and it needs Obsidian to be open with the plugin enabled, because the plugin is the only way in. The README pins the mcp Python SDK below 2.0, since the server uses the 1.x low-level API that 2.0 removed. The repo had 4,456 GitHub stars on 2026-10-01; its last push was on 2026-08-31.

Tools it gives your agent

• list_files_in_vault
• list_files_in_dir
• get_file_contents
• search
• patch_content
• append_content
• delete_file

When to use Obsidian

• You want the agent to find every note that mentions a topic and explain the context.
• You want a summary of last week's meeting notes written into a new note.
• You keep project docs in Obsidian and want the agent to read them while it codes.
• You want to add tasks or links under a specific heading without opening the app.

When to pick something else

• Vaults you cannot afford to lose: the server can delete files and folders, so keep a backup or Obsidian Sync history before letting an agent write.
• Use without the Obsidian app running: every call goes through the Local REST API plugin, so the app must be open on the same machine or reachable on the network.
• Official support: the server is community-maintained and not published by Obsidian.

What Obsidian needs

• Obsidian with the Local REST API community plugin installed and enabled, and its API key
• Python 3.11 or newer with uv (uvx), or Docker

What the Obsidian MCP server costs

Free and open source under MIT; it needs the Obsidian app and the free Local REST API plugin, with nothing to pay.

Current prices: github.com ↗. We do not list prices: vendors change them often, so check the publisher's own page.

Other MCP servers for notes, docs and team tools

• Atlassian: The Atlassian MCP server gives AI agents access to Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom on Atlassian Cloud: search, summarize, and create or update issues and pages.
• Linear: The Linear MCP server gives AI agents access to your Linear workspace through Linear's hosted endpoint: find, create and update issues, projects and comments, with a read-only URL when you only need lookups.
• Notion: The Notion MCP server gives AI agents access to your Notion workspace through Notion's hosted server: search pages and databases, read them as Markdown, and create or update pages, databases and views.
• Slack: The Slack MCP server gives AI agents access to a Slack workspace through Slack's hosted endpoint: search messages and files, read channels and threads, send messages, and edit canvases and lists.