Obsidian doesn’t ship an MCP server of its own, so you pick one. There are four community options, and since May 2026 the Local REST API plugin serves MCP itself, which makes the old two-install setup optional.
For most vaults the simplest one is enough, and it takes about five minutes in Claude Desktop, Claude Code or Codex.
- Best overall: the Local REST API plugin. Since version 4.0 it serves MCP itself at
/mcp/, so it is one install rather than two. - Fastest setup: Filesystem MCP pointed at your vault folder. No plugin, no API key, under five minutes, and it works whether or not Obsidian is open.
- Most tools: obsidian-mcp-server by cyanheads. 14 tools covering frontmatter, tags, templates and the Obsidian command palette.
- Skip mcp-obsidian unless your client forces it. It wraps the same REST API as a separate install. Claude Desktop is the one client that still needs a bridge, and that bridge is
mcp-remote. - Skip the config: Context Board opens your vault in a browser, and its chat runs on the Claude Code or Codex you already pay for, reading and editing your notes.
Does Obsidian have an MCP server?
No. Obsidian ships a command line interface (1.12 and later), and it doesn’t speak MCP. The closest thing to built-in is the community Local REST API with MCP plugin, which has served MCP at /mcp/ since version 4.0.
The Model Context Protocol is an open standard released by Anthropic in late 2024 for how AI clients talk to external tools. For Obsidian, an MCP server lets Claude list your files, read and search notes, write new ones and edit existing ones, without copy-paste. If you want the background first, What is MCP covers it.
Two routes exist. The official Filesystem MCP server treats your vault as what it is on disk, a folder of Markdown. The Obsidian Local REST API plugin treats it as a running Obsidian and talks to it over an authenticated local HTTP API. That second route used to need a separate bridge, mcp-obsidian. Since version 4.0 the bridge is a fallback.
Filesystem MCP or the Local REST API?
The Obsidian forum threads on this go back and forth. The useful question is which one fits the work you do in your vault.
| Dimension | Filesystem MCP | Obsidian Local REST API (built-in MCP) |
|---|---|---|
| Plugin required? | No | Yes (Local REST API community plugin) |
| Works when Obsidian is closed? | Yes | No |
| Read and write notes | Yes | Yes |
| Uses Obsidian’s own search index | No (matches file names, not note text) | Yes |
| Atomic note updates (patch by heading or block) | No | Yes |
| Triggers link graph updates live | No (needs Obsidian to re-scan on open) | Yes |
| Memory footprint | Low | Higher (Obsidian must run) |
| Auth model | Folder allowlist | API key in config |
| Best for | Daily knowledge work, drafting, retrieval | Power workflows, atomic edits, template execution |
If you mostly read notes and write new ones, use Filesystem MCP. If you depend on Dataview queries, Templater scripts or surgical edits to one heading inside a long note, the REST API is worth the plugin overhead.
My advice is to start with Filesystem and stay there until a feature forces the move. Keeping Obsidian open and the plugin updated costs more than the richer features return in daily use. Our Filesystem MCP server guide covers its full tool surface and the directory scoping that keeps it safe.
Path 1: Filesystem MCP
Five minutes, one config edit, one restart.
Step 1. Find your vault path: In Obsidian, open the vault settings (the cog icon, then About). The path is shown at the top. On macOS it usually lives in ~/Documents/ObsidianVaults/YourVault. On Windows it tends to be under C:\Users\you\Documents\ObsidianVaults\YourVault. Copy the full path.
Step 2. Open the Claude Desktop config file: In Claude Desktop, go to Settings, then Developer, then Edit Config. That opens claude_desktop_config.json, or creates it if it’s missing. On macOS the file lives at ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows it lives at %APPDATA%\Claude\claude_desktop_config.json.
Step 3. Add the Filesystem MCP server: Point it at your vault path. Multiple allowed paths are supported, so you can include other folders you want Claude to touch.
{
"mcpServers": {
"obsidian-vault": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/you/Documents/ObsidianVaults/YourVault"
]
}
}
}
Step 4. Fully quit and reopen Claude Desktop: Cmd-Q on macOS, fully close on Windows. A window reload doesn’t pick up new MCP servers, and it’s the usual reason a new server isn’t showing up.
Step 5. Test it: Open a new chat and ask “list the files in my Obsidian vault” or “find the notes with Q3 in the file name.” The official MCP servers repo covers the same install pattern if you want more context.
Claude can now list files, read any file, write new ones, edit existing ones, search by file name pattern, and move or rename. It matches file names, not the text inside notes, so “which notes mention pricing” means Claude has to open files to check. Performance is good even on 10,000-note vaults, because there’s no Obsidian process, plugin layer or HTTP round trip in the path.
What it can’t do is anything Obsidian itself knows. It can’t refresh the graph, run Dataview queries or execute a Templater template. For those, see path 2.
Path 2: Local REST API, which now serves MCP itself
Take this path if you live inside Obsidian and want Claude to act on the running app as well as the files. It has more steps and more depth.
Step 1. Install the plugin: In Obsidian, open Settings, then Community plugins, then Browse. Search for “Local REST API with MCP” by coddingtonbear. Install it and enable it.
Step 2. Copy the API key: Open the plugin settings and copy the key. By default the plugin runs at https://127.0.0.1:27124 with a self-signed certificate. The plain HTTP endpoint at http://127.0.0.1:27123 is off by default. To skip the certificate step, turn it on under Settings, then Local REST API, then Enable HTTP server. The key is your only auth, so treat it like a password and keep it out of any repo.
Step 3. Point your client at the plugin’s MCP endpoint: The plugin serves MCP at https://127.0.0.1:27124/mcp/, with the same key sent as a bearer token. Your client either has to trust the plugin’s certificate (download it from https://127.0.0.1:27124/obsidian-local-rest-api.crt) or you use the HTTP endpoint from step 2 at http://127.0.0.1:27123/mcp/. Claude Code, Codex and Cursor speak that transport natively, so there’s no third install. Commands for Claude Code and Codex are in the next section.
Step 4. Wire it into Claude Desktop: Claude Desktop is the one client that still needs a bridge. Its custom connectors are called from Anthropic’s cloud, which can’t see 127.0.0.1 on your machine, and its config file only starts local commands. The bridge is mcp-remote. Save the plugin’s certificate from step 3 somewhere permanent first, because mcp-remote runs on Node, and Node refuses a certificate it hasn’t been told to trust. Then edit claude_desktop_config.json as before.
{
"mcpServers": {
"obsidian": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://127.0.0.1:27124/mcp/",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer your-api-key-here",
"NODE_EXTRA_CA_CERTS": "/Users/you/obsidian-local-rest-api.crt"
}
}
}
}
The key sits in env rather than args on purpose. The mcp-remote README notes that Claude Desktop on Windows doesn’t escape spaces inside args, so Authorization: Bearer ... written straight into the list breaks there and the server never starts.
Step 5. Keep Obsidian open while you use it: The plugin only responds when Obsidian is running. If you close the app, the MCP calls fail. If you keep Obsidian open all day you won’t notice. If you only open it when you need a note, this path is the wrong fit.
In return you get atomic patch operations (edit one heading without touching the rest of the file), search through Obsidian’s own indexer, which handles aliases, wikilinks and frontmatter the way Obsidian does, and link graph updates as Claude writes. The Obsidian forum showcase thread has user reports from both setups.
Obsidian MCP in Claude Code and Codex
Coding agents skip the JSON file and the bridge. Both take a one-line command for the Filesystem path and speak HTTP MCP natively for the Local REST API path.
Claude Code
For the Filesystem path, run this once with your own vault path. The --scope user flag makes the server load in every project, not only the folder you ran it from.
claude mcp add --scope user obsidian-vault -- npx -y @modelcontextprotocol/server-filesystem /Users/you/Documents/ObsidianVaults/YourVault
For the Local REST API path, point it at the plugin’s endpoint and pass the key as a header.
claude mcp add --scope user --transport http obsidian https://127.0.0.1:27124/mcp/ --header "Authorization: Bearer your-api-key-here"
Type /mcp inside Claude Code to check the server shows as connected. If it says failed to connect, match the reason to its fix. If it reports a certificate error, trust the plugin’s certificate from step 3 or swap the URL for the HTTP endpoint, http://127.0.0.1:27123/mcp/.
Codex
The Filesystem path is one command too.
codex mcp add obsidian-vault -- npx -y @modelcontextprotocol/server-filesystem /Users/you/Documents/ObsidianVaults/YourVault
For the Local REST API path, add a table to ~/.codex/config.toml. OpenAI’s MCP docs for Codex cover the url and bearer_token_env_var keys and say nothing about trusting a custom certificate, so use the plugin’s HTTP endpoint here. Turn it on under Settings, then Local REST API, then Enable HTTP server. By default it only listens on 127.0.0.1, so the traffic stays on your machine.
[mcp_servers.obsidian]
url = "http://127.0.0.1:27123/mcp/"
bearer_token_env_var = "OBSIDIAN_API_KEY"
Set OBSIDIAN_API_KEY as a user-level environment variable, not only in one shell. The CLI, the IDE extension and the ChatGPT desktop app read the same config, so one setup covers all three. If the Filesystem server times out on its first run while npx downloads the package, add startup_timeout_sec = 30 to its table, since the default is 10 seconds.
The four community Obsidian MCP options compared
The Filesystem path above is the official Anthropic server pointed at a vault folder. These are the community servers that come up again and again in forum threads and GitHub stars, compared on what decides the pick.
| Option | Plugin needed | Obsidian must be open | Edit model | Best for | 2026 activity |
|---|---|---|---|---|---|
| mcp-obsidian (MarkusPfundstein) | Local REST API | Yes | Atomic patch by heading or block | Clients with no HTTP MCP support and no Node for mcp-remote, now that the plugin serves MCP itself | About 4,500 GitHub stars, more than the other two servers here combined; widely cited in forum threads |
| obsidian-mcp-server (cyanheads) | Local REST API | Yes | 14 tools, including section-aware PATCH, tag manager, frontmatter | Power users who want the deepest tool set on top of the REST API | Active; TypeScript stack, v3.7.0 released October 2026, needs Local REST API 4.0 or later |
| MCPVault (bitbonsai) | No | No | Direct filesystem with AST-aware frontmatter preservation | People who want the Filesystem MCP feel with safer YAML handling | Renamed to @bitbonsai/mcpvault on npm in March 2026; multiple April 2026 releases |
| Eleanor Konik’s pattern (Filesystem MCP + workflow) | No | No | Plain Filesystem MCP; complexity lives in the prompts and scripts | Writers who want a minimal stack and rely on Claude to run scripts on the vault | Documented across her Substack posts; no custom server to maintain |
mcp-obsidian by MarkusPfundstein
Most forum threads land on this one. It’s a Python MCP server that wraps the Local REST API plugin and exposes around ten tools: list files, read file, full-text search, append, patch by heading or block, delete, and a couple of daily-note helpers. Atomic patch is the standout. You can ask Claude to “add this bullet under the Q3 heading in my project file” and the rest of the file stays untouched.
It installs through uvx mcp-obsidian, so there’s no venv to set up if you have uv. The MarkusPfundstein/mcp-obsidian repo has the full install path and an example Claude Desktop config.
The dependency chain is one link longer than it needs to be since May 2026. You install the plugin, enable it, copy a key and keep Obsidian running, and the plugin already serves MCP on its own. The Python layer on top only earns its place if your client can’t reach an HTTP MCP server and can’t run mcp-remote either.
obsidian-mcp-server by cyanheads
The same REST API foundation with more tools on top. The obsidian-mcp-server repo documents 14 tools grouped by shape. Readers fetch notes and metadata. Writers create or surgically edit content. Managers reconcile tags and frontmatter. A guarded escape hatch dispatches Obsidian command-palette commands, and it stays off until you set OBSIDIAN_ENABLE_COMMANDS.
Search is stronger too, with three modes: plain text, JSONLogic, and BM25-ranked Omnisearch when that plugin is reachable at startup. Setup overhead is the same as mcp-obsidian, so pick this one if you want more tools on the REST API path.
MCPVault by bitbonsai
Filesystem MCP, but smarter about YAML. It doesn’t need the Local REST API plugin or an open Obsidian. It reads and writes Markdown files directly, with two upgrades over plain Filesystem MCP.
First, frontmatter. MCPVault uses gray-matter with AST-aware updates that preserve the raw formatting of any field Claude doesn’t modify. Plain Filesystem MCP will happily reformat a whole frontmatter block when it rewrites a file.
Second, path safety. The server filters the .obsidian directory and other system files by default, and patched a symlink path-traversal vulnerability in v0.9.1 (March 2026). The package was renamed to @bitbonsai/mcpvault on npm at Obsidian’s request that same month. If the Filesystem path feels right but you’ve hit the YAML-reformatting problem, swap it in and the rest of your setup stays the same.
Eleanor Konik’s minimal pattern
This one isn’t a server, it’s a workflow. Eleanor Konik writes about her Claude and Obsidian setup on her Substack, and her stack is plain Filesystem MCP pointed at a local vault. No plugin, no bespoke server. The complexity lives in the prompts.
She has Claude brute-force-search across notes for word combinations, write small Python scripts that update filenames or migrate Dataview metadata into Obsidian Bases, and compile information from several linked notes into one report. For most writers that’s the setup to copy, since clearer prompts and a tidier vault matter more than a richer server.
Why does Obsidian MCP say “Server disconnected”?
In Claude Desktop, “Server disconnected” means the server process started and died, or never started. The message is the same whatever the cause, so read the log before you change anything. On macOS the logs are in ~/Library/Logs/Claude, on Windows in %APPDATA%\Claude\logs, and each server writes its own mcp-server-<name>.log file.
- Obsidian is closed: The Local REST API path, mcp-obsidian and the cyanheads server all talk to the running app. Open Obsidian, then fully quit and reopen Claude Desktop.
- The command is not found: Claude Desktop doesn’t start servers from your terminal, so
npxoruvxmay not be on the path it sees. A log line likespawn uvx ENOENTorspawn npx ENOENTis this. Put the full path incommand(runwhich uvxon macOS orwhere uvxon Windows), or install Node 18 or later ifnpxis missing. If a command hangs, check thatnpxhas-y, since without it npx waits on an install prompt Claude can’t answer. - The certificate is refused:
mcp-remotewon’t connect tohttps://127.0.0.1:27124until Node trusts the plugin’s certificate. SetNODE_EXTRA_CA_CERTSas in path 2, or use the HTTP endpoint. - The key is wrong or empty: A 401 in the log means the plugin rejected the request. Copy the key from the plugin settings again. On Windows, keep the
Bearerheader inenv, as in path 2. - The JSON does not parse: One missing comma and Claude Desktop starts none of the servers in the file. Paste the file into any JSON validator before you restart.
If the log shows MCP error -32000: Connection closed, the server exited before it finished connecting, and the lines above it usually name the reason.
Two more causes are worth ruling out. If list_files returns nothing, or only a .obsidian folder, your vault path is wrong; symlinks, iCloud Drive and OneDrive paths trip people up. And past ten MCP servers you’ll feel the startup and memory cost, so three to six is a better range.
Where Context Board fits next to Obsidian
An MCP server gives Claude a way into your vault. It doesn’t give you a place to watch what Claude does there. You ask in a chat, Claude edits a note, and you switch to Obsidian to see what changed.
Context Board covers that. A Files board opens the vault folder from your own computer in a browser tab: the folder tree, [[links]], backlinks, tags, search, and a live-preview editor. A small program called the runner, installed with one line, opens only the folders you choose, each read only or read and write. The board keeps no copy of your notes.
The board’s chat runs on the Claude Code or Codex you already pay for, so there’s no API key and no extra bill. It knows which note you have open, so “tidy this note” or “what links here?” works, and each edit shows in the note as it lands. You can keep Obsidian for writing. Context Board is free for 3 days, then $12 a month. Open your Obsidian vault in a browser has the setup.