Claude + Obsidian: What the Integration Can (and Can't) Do in 2026
There’s no official Claude Obsidian connector — and yet Obsidian is one of the best-connected apps in the Claude ecosystem. Anthropic’s directory has no Obsidian entry, and Obsidian’s stated posture is to enable the ecosystem rather than ship first-party AI (there’s an open feature request for an official MCP core plugin). But because a vault is just a folder of markdown, three real routes exist: the community Local REST API with MCP plugin (which since v4 ships its own MCP server), Obsidian’s official CLI and headless Sync client from the 1.12 release, and Claude Code working directly on the vault files. All three are local — and that’s also the limit: nothing here runs while you’re away, and claude.ai on the web can’t reach a vault on your disk.
Here’s each route, when to pick it, and what to use when you want vault work that happens without you at the keyboard.
Route 1: the Local REST API with MCP plugin (Claude Desktop)
The plugin most setups route through is Local REST API with MCP (coddingtonbear, 2,600+ stars). Since v4.0 (May 2026) it includes a built-in MCP server — tools like vault_read, vault_patch, and search_query — so the separate bridge server older tutorials describe is no longer required. The plugin was renamed to “Local REST API with MCP” in v4.1.1 to make that explicit.
Setup: install the plugin from Obsidian’s community plugin browser, copy its API key, and add the MCP server to claude_desktop_config.json (or install it as a desktop extension). Claude Desktop can then read notes, search the vault, and patch files in place — “find every note tagged #project without a status line and add one” works.
Two notes for existing users:
- Update the plugin. v4.1.3 (June 2026) patched an authenticated path-traversal vulnerability (GHSA-62gx-5q78-wrvx). If you’re on an older v4, upgrade before wiring anything to it.
- If you followed a 2025-era guide, you probably installed mcp-obsidian (MarkusPfundstein, 4,000+ stars) — a standalone stdio server that talks to the same plugin. It still works and remains the most-installed option, but it’s now an extra hop the plugin can do itself. obsidian-mcp-tools is worth a look if you want semantic search and Templater prompts on top.
Requirement for all of these: Obsidian must be running, and it’s Claude Desktop (or Claude Code) only.
Route 2: Claude Code straight on the vault
A vault is markdown files in a folder — which means Claude Code can operate on it with no plugin at all. Point it at the vault directory and it can grep across thousands of notes, refactor frontmatter in bulk, fix broken wikilinks, split monster notes, or generate a MOC from a folder. For batch operations this is often better than the MCP route, because Claude Code can run scripts over the whole vault instead of patching one note per tool call.
The zero-plugin middle ground: Anthropic’s reference Filesystem MCP server pointed at the vault folder gives Claude Desktop read/write access to the raw markdown, no REST API involved. You lose Obsidian-aware niceties (search that understands tags and links) but gain simplicity.
Route 3: Obsidian’s official CLI and headless Sync
The official piece arrived with Obsidian 1.12 (February 2026): an official CLI with full vault control from the terminal — create, read, append, move, delete, vault-wide search, tags and backlinks, daily notes, plugin control, Bases queries — and a headless Sync client (obsidianmd/obsidian-headless) that syncs vaults on servers without the desktop app. The CLI docs explicitly call out agentic coding tools as an audience.
For self-hosters this unlocks the closest thing to server-side Obsidian automation that exists: obsidian-headless keeps a vault synced on a VPS, and scripts (or Claude Code sessions) run the CLI against it on cron. It’s genuinely powerful — and it’s still infrastructure you build and babysit yourself, not a hosted API. Obsidian Sync is end-to-end encrypted with no public REST API, deliberately.
The limits that actually matter
- Local only. Every route above touches a vault on a machine you control. claude.ai in the browser cannot reach it — this is Claude Desktop / Claude Code territory.
- No triggers. Claude reads and writes the vault inside a session you start. There’s no “when a meeting ends, append the summary to today’s daily note” — nothing fires on an event.
- Laptop-bound for anything scheduled. Claude Cowork’s scheduled tasks run on a fixed clock, not on inbox events. The headless-CLI route escapes that, but only by making you the operator of a small server.
So Claude is excellent for “work on my vault with me right now” — and not built for “keep notes flowing into my vault while I’m in meetings.”
If you want Obsidian work that runs on its own: Carly
Obsidian has no cloud API — but a vault synced through Google Drive, Dropbox, or iCloud is reachable by anything that can write markdown files. That’s the honest bridge, and it’s the one Carly uses: Carly writes to Drive and Dropbox natively, so a markdown file she drops into the synced folder simply appears in Obsidian.
Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- After every meeting, Carly writes a markdown summary with action items into a
Meetings/folder in your synced vault — it’s in Obsidian before you’re back at your desk. - Every weekday at 7am, she compiles your calendar and flagged emails into
Daily/2026-07-11.md, matching your daily-note format. - When you forward an article or ask for research, the summary lands as a markdown file tagged
#inboxin the vault, ready to process on your terms. - No-code setup. Describe the flow in plain English; Carly interviews you and builds it.
- Actually sends — drafts and sends email across Gmail and Outlook, manages tasks, updates your CRM.
- Connects to anything — 200+ native integrations, plus any tool with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude (MCP / CLI / Claude Code) | Carly | |
|---|---|---|
| Read and search your vault | Yes (Desktop + plugin, or Claude Code) | No — writes into the synced folder |
| Edit notes in a session | Yes | — |
| Bulk refactors across the vault | Yes (Claude Code shines here) | No |
| New notes appear without you prompting | No | Yes (Drive/Dropbox-synced folder) |
| Acts on triggers / schedules | No (DIY with headless + cron) | Yes, built in |
| Works while laptop is closed | No (unless you run a VPS) | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is the best thinking partner inside your vault. Carly is the feed that keeps the vault stocked while you’re elsewhere.
Frequently Asked Questions
Does Claude work with Obsidian?
Yes, well — just not through an official connector. The main routes are the community Local REST API with MCP plugin (built-in MCP server since v4, May 2026) with Claude Desktop, Claude Code working directly on the vault’s markdown files, and Obsidian’s official CLI/headless Sync client (v1.12) for scripted setups. All are local; there’s no Anthropic or Obsidian first-party connector.
Which Obsidian MCP server should I use in 2026?
Start with the Local REST API with MCP plugin itself — since v4 it ships its own MCP server, so the separate mcp-obsidian bridge is optional. Make sure you’re on v4.1.3 or later (path-traversal fix). If you don’t need Obsidian-aware search, Anthropic’s Filesystem MCP server pointed at the vault folder is the simplest option of all.
Can claude.ai on the web access my vault?
No. Your vault lives on your disk and Obsidian Sync has no public API, so the browser version of Claude can’t reach it. Vault access requires Claude Desktop with a local MCP server, or Claude Code in the vault directory.
Can Claude add notes to my vault automatically?
Not on its own — MCP tools run inside a session you start, and scheduled tasks require your machine to be awake. The practical pattern for automatic capture is a synced vault folder: Carly drops markdown (meeting summaries, daily briefs, research) into a Drive- or Dropbox-synced folder and Obsidian picks it up on sync. AI agents start at $35/month.
More: Notion vs Obsidian · Claude + Notion · Claude + Mem · Claude connectors · Can Claude send emails · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
