Skip to content
Wenlan

Developer workflow

Obsidian + Claude Code: Connect Your Vault and Check Answers

Connect Claude Code to Obsidian, find notes for a project without knowing their filenames, and check the latest decision against its sources. Includes setup, a tested search prompt, and example results; MCP and plugins are optional.

Qi-Xuan LuUpdated 12 min read

01

An Obsidian vault is a folder of Markdown files. Run Claude Code in that folder and it can already read, search, and edit your notes.

02

Find the right project notes, separate current decisions from copied old messages, and check the sources before acting.

03

Wenlan is a personal wiki built for AI to organize and maintain knowledge. Page creation, source tracking, and revision review are built in. Connect your Obsidian notes, or use Wenlan on its own.

01

Quick answer

You don't need a plugin to use Claude Code with Obsidian. Open a terminal in your vault folder and run claude. Claude Code can then read, search, create, and edit notes in that folder, within its access permissions.

Prefer not to use a terminal? With a Claude Pro, Max, Team, or Enterprise subscription, open Claude Desktop’s Code tab, choose Local, and select your practice vault as the project folder. You can then use the same two-note exercise below.

Start with the setup and two-note exercise below. You will ask for the current project decision, check the cited notes, and separate confirmed details from what remains unknown. Add the tools in this table only when you need their extra features:

SetupWhat it addsGood for
Claude Code in the vault folderRead, write, and search every Markdown fileAlmost everyone; start here
CLAUDE.md in the vaultStanding instructions: folders, note style, what not to touchConsistent results every session
Obsidian CLI + Obsidian skillsBacklinks, Obsidian search, tasks, and correct Obsidian syntax, Bases, and CanvasVaults that rely on links and Obsidian features
Obsidian MCP serverVault tools for MCP clientsNormal Claude chats and shared access across clients
Plugin inside Obsidian (Claudian)Claude Code chat in an Obsidian sidebarPeople who don't want to use a terminal

02

Before you start: install and sign in

This guide uses the Claude Code terminal app on a desktop computer. Install Claude Code with the official instructions for your operating system, then run claude --version to check that your terminal can find it. Start claude and complete sign-in before connecting your vault. You need a supported Claude subscription, Console API account, or configured provider; installing an Obsidian plugin does not include model access.

For a first attempt, create a separate practice vault containing only the two fictional notes below. Replace ~/Documents/MyVault in the command with that vault’s actual path; put paths containing spaces in quotes. Do not start with your entire personal archive.

The terminal steps below are for the CLI route. If you use the Desktop Code tab, select the practice vault there and skip to the two-note exercise.

Claude Code installation and sign-in instructions

03

Step 1: Run Claude Code in your Obsidian vault

Your vault is the folder you picked when you created it in Obsidian. Start Claude Code there. Obsidian shows changes as soon as Claude Code saves a file, so you can keep both open side by side.

If you're already working in another project, add the vault as an extra folder instead of switching.

  • Back up first. Put the vault under git or use Obsidian Sync version history, so you can undo a bad edit.
  • Start with the read-only two-note exercise below before asking Claude to edit or reorganize your notes.
  • Claude Code sends the text it reads to your configured model provider. Keep private folders outside the practice vault; a prompt asking it not to read a folder is not an access restriction.
Start Claude Code in the vault
cd ~/Documents/MyVault
claude

# or, from another project folder:
claude --add-dir ~/Documents/MyVault

04

First task: find the latest project decision across two notes

In your practice vault, create the two Markdown notes below and paste the corresponding text into each. This is a fictional exercise: the later note changes a date but leaves one question unanswered. No MCP server, Obsidian CLI, or plugin is needed.

After starting Claude Code in that vault, paste the prompt below into its conversation. The task is to read and answer, not reorganize or rewrite the notes.

NoteText to paste
01-plan.mdMeeting on October 1: demo planned for October 20. Owner: Mei. Venue still to be confirmed.
02-update.mdUpdate on October 3: demo moved to October 22. Mei remains the owner. No venue has been confirmed.
Ask inside Claude Code, not in your shell
Read 01-plan.md and 02-update.md.
Do not create, edit, move, or delete files.
What is the current demo date, who owns it,
and what still needs confirmation?
For each answer, name the source file and quote
the supporting sentence. Distinguish the old date
from the new one. Do not fill in missing details.

05

Check the answer before using your own notes

The answer should say October 22, Mei, and venue not yet confirmed. October 20 is the superseded date. Open the named source notes yourself: the updated date must come from 02-update.md, and a specific venue would be invented.

If Claude cannot find a file, check the working folder and spelling first. If it uses the old date, ask it to compare the two dated statements. If it invents a venue, have it mark the value unknown. Keep both original notes unchanged; once you can verify this small answer, repeat with a few non-sensitive notes from one real project.

You have now checked a useful first outcome: finding a current decision across notes with evidence you can inspect. CLAUDE.md, the CLI, MCP, and plugins below are optional additions for recurring work. This exercise does not establish that an AI can safely organize your whole vault.

Want this answer to become knowledge you can keep using as the project changes? Wenlan has page creation, source tracking, and revision review built in, so you do not have to assemble that maintenance workflow yourself. Try it with your Obsidian notes in the exercise below.

Practice-run answer excerpt — layout shortened
Current date: October 22
02-update.md: “Update on October 3:
demo moved to October 22.”

Owner: Mei
02-update.md: “Mei remains the owner.”

Still unknown: venue
02-update.md: “No venue has been confirmed.”

Old date, now superseded: October 20
01-plan.md: “Meeting on October 1:
demo planned for October 20.”

Connect Obsidian to Wenlan: try a project brief

06

Search your existing vault when you don't know the filenames

In your own vault, the hard part may be finding the relevant notes in the first place. Start with one project and a few non-sensitive folders. The prompt below is for the fictional Harbor demo. For your own task, replace the question, time period, project name, starting folder, optional archive folder, and requested facts. Keep the checks for sources, old decisions, unknowns, and search coverage.

Ask for the source notes and their dated statements, not just a confident answer. A recently saved file can quote an old message. If two decisions conflict and the notes do not say which replaces the other, the answer should show the conflict rather than choose a date for you.

  • Open the named notes and check the supporting sentences. A citation only helps if the note actually supports the claim.
  • If a source is missing, name the project, an alternate name, or another folder to search. A failed search does not prove the information is absent from your vault.
  • This is a read-only request, not an access restriction. For an isolated first run, use a separate folder containing only the notes you intend to share with your model provider.
Find the sources before answering — paste into Claude Code
Find the latest decision about the Harbor demo in October 2026
in this vault.
Start with Projects/Harbor/; check Archive/ only if a source
points there or the current notes are insufficient.
Do not create, edit, move, or delete files.
First find and read relevant notes; do not rely on filenames
or file modification times as evidence of a decision.
Return the current demo date, owner, duration, and what must
happen before invitations can be sent.
For each fact, give the note path, its dated statement, and
a short supporting quote. Separate superseded dates and
copied old messages from the current decision.
Mark missing information unknown.
Finish with one next action, the folders actually searched,
and any files you could not read.

Inspect the six fictional notes, prompt, and expected results

07

What the project search found — and what it left unchecked

We ran this prompt with six fictional notes: four about Harbor's current demo, one archived Harbor demo from 2025, and one note for another project. We gave Claude the project and folder, without naming the individual files. It found and read the four current-project notes. These are the results, condensed from that practice run:

ResultSource under Projects/Harbor/What to check
Demo: October 22; owner: Mei2026-10-03-demo-update.mdThe October 3 decision explicitly replaces the October 1 plan for October 20
Duration: 15 minutes2026-10-04-invitations.mdThe checklist supplies the duration and says to wait for venue confirmation before sending invitations
Venue: still unknown2026-10-03-demo-update.mdThe source says no venue has been confirmed; do not borrow a venue from another project
October 20 is a copied old message2026-10-05-chat-excerpt.mdThe October 5 file quotes an October 1 message and explicitly says it is not a new decision
  • The next action was for Mei to confirm the venue before sending invitations. Claude reported that it had not read Archive/ or the other project's note; this was not a search of every note in the vault.
  • We then changed the decision inside the demo-update note to October 7, moving the demo to October 24, and repeated the same prompt in a fresh session. It returned October 24 and identified the dated statement inside the file, although the filename still said October 3.
  • Neither Claude run changed a source file. This small practice run shows what to inspect; it does not establish accuracy across a large personal vault.
  • When using this with your own project, check the current decision and next action against the cited notes. If you want a brief you can keep updating from those sources, try the Wenlan exercise below.
Keep a project brief and update it when a source changes

08

Optional: Add a CLAUDE.md to the vault

Claude Code reads CLAUDE.md from the folder it starts in at the beginning of every session. Use it to explain how your vault is organized, so you don't repeat it every time.

~/Documents/MyVault/CLAUDE.md
# My vault

- Notes use [[wikilinks]], not Markdown links.
- New notes go in Inbox/. Never move files out of Archive/.
- Daily notes live in Daily/ as YYYY-MM-DD.md.
- Put AI-written summaries in AI/, not next to my own notes.
- Never edit anything inside .obsidian/.

09

Optional: Add the Obsidian CLI and Obsidian skills

Claude Code can read the text and frontmatter in your notes. The Obsidian CLI adds access to Obsidian's own search and backlink tools, along with commands to read tasks and append to the daily note.

Install the current Obsidian installer (1.12.7 or later), then enable Settings > General > Command line interface and follow the registration prompt. Restart your terminal afterward. Obsidian must be running; the first command opens it if needed.

  • Obsidian skills (kepano/obsidian-skills) teach Claude Code to use the Obsidian CLI and write Obsidian-style Markdown, Bases, and JSON Canvas files.
  • Install them as a Claude Code plugin: /plugin marketplace add kepano/obsidian-skills, then /plugin install obsidian@obsidian-skills.
  • The same skills work in Codex and other tools that support Agent Skills.
Obsidian CLI commands Claude Code can run
obsidian search query="meeting notes"
obsidian backlinks file=Recipe
obsidian tasks todo
obsidian daily:append content="- [ ] Follow up"

10

Obsidian MCP server: when you need one

Claude Code can already reach your files, so an MCP server is usually optional there. A normal Claude Desktop chat needs MCP to use vault tools. Claude Desktop's Code tab also offers Local folder access: choose your practice vault there if you prefer not to use a terminal. MCP is also useful when you want the same vault tools in several clients.

The Local REST API community plugin now includes an MCP server. Install and enable it in Obsidian, copy the API key from Settings > Local REST API, then add it to Claude Code. Obsidian must be running for the server to answer.

The command below configures Claude Code only. For the separate Claude Desktop Chat tab, follow the Local REST API documentation’s Claude Desktop setup; this CLI command does not configure that chat.

  • The plugin uses its own certificate. If the connection fails, trust its certificate or enable the plain HTTP server on port 27123 in the plugin settings.
  • mcp-obsidian is an older Python server that talks to the same plugin through uvx.
  • Keep the API key out of shared files such as a committed .mcp.json.
Add the Obsidian MCP server to Claude Code
claude mcp add --transport http obsidian https://127.0.0.1:27124/mcp/ \
  --header "Authorization: Bearer <your-api-key>"

Local REST API: separate Claude Code and Claude Desktop setup

11

Obsidian plugins for Claude Code

If you'd rather not use a terminal, a plugin can run Claude Code inside Obsidian. You still need Claude Code installed and signed in.

PluginWhat it doesInstall
ClaudianRuns Claude Code or Codex in an Obsidian sidebar with your vault as the working folderCommunity plugins: search "Claudian"
Claude Code IDE bridge (obsidian-claude-ide)Shares the active file and selection with Claude Code running in a terminalSettings → Community plugins → Browse → search `Claude Code IDE`; install and enable, then run `/ide` in the Claude Code terminal and select Obsidian
obsidian-claude-code (Roasbeef)An embedded Claude assistant inside the vaultFrom GitHub
obsidian-claude-code-mcp (iansinnott)MCP and IDE bridge for Claude Code; last updated in 2025From GitHub

12

Build a second brain with Claude Code and Obsidian

A common workflow starts with an inbox for articles, meeting notes, or transcripts. Claude Code reads those files, writes summary notes, links them to existing notes, and files them. The claude-obsidian starter kit packages this workflow as Claude Code skills.

As AI-written notes accumulate, it can become harder to distinguish your own writing from AI inferences, or spot summaries that no longer match their sources.

  • Keep AI-written notes in their own folder.
  • Ask Claude Code to link every summary back to the note or file it came from.
  • Review changes with git diff before you commit them.
  • Re-check summaries when the original note changes.

13

Already using Obsidian with AI? When Wenlan helps

Wenlan is a personal wiki built for AI to organize and maintain knowledge. Creating pages, preserving sources, tracking changes, and reviewing revisions are built in. You do not have to assemble and maintain a separate set of plugins, scripts, and rules for those tasks.

You can start directly with documents, notes, and AI work; Obsidian is optional. Use your connected AI to save and retrieve knowledge, then open Wenlan when you want to read a page, check its sources, or review changes. If you still want Obsidian’s editor and plugins, keep using them and connect your vault.

Obsidian’s Markdown files can already be read and edited by different AI tools with access. Projects such as claude-obsidian also provide citations and maintenance workflows. Wenlan offers its own built-in workflow; cross-AI access alone is not the reason to choose it. If your existing setup already suits you, you may not need another tool.

In this exercise, the useful result is a project brief you can return to when the demo date changes from October 22 to October 24. You update the same page from the new source and check its evidence; a later task can use that page instead of relying on an old answer in a chat.

Your Obsidian vault connects as a source: notes stay in Obsidian, and Wenlan never edits them without your OK; it writes a change only when you accept it. Wenlan follows the vault in the background, checking about every 30 seconds, so after editing a note you can ask your connected AI to update the page without a manual resync. Background page updates require a configured model. If AI updates a page you have edited, it proposes a revision for you to review. AI handles the organizing; you still judge the content.

NeedUseful approach
Look up a few notesAsk Claude to read the files directly
Automate vault organizationUse skills or plugins such as claude-obsidian
Use a built-in workflow for creating and maintaining knowledge pagesTry Wenlan, with or without Obsidian
See how source-backed wiki pages work

14

Keep a project brief in Wenlan

If you want to keep updating a brief after the chat ends, try this optional Wenlan exercise. Connect Wenlan to Claude Code with the commands below before starting.

Keep the two practice notes and add 03-checklist.md below. With the default settings in Wenlan 0.18.16, a distilled Page needs at least three distinct source memories; these three short notes provide one each.

Add this noteText to paste
03-checklist.mdChecklist on October 4: allow 15 minutes for the demo. Send invitations only after the venue is confirmed.
  • In the Wenlan desktop app, open Settings → Sources. Add the practice vault as an Obsidian source and wait for all three notes to sync.
  • Ask Claude: “Use Wenlan to find 01-plan.md, 02-update.md, and 03-checklist.md from my practice vault. Create a project brief from those sources. Include the current demo date, owner, duration, and what remains unknown. Keep the short summary about the page’s purpose; put the schedule details in the body. Return the Page ID so I can update the same page later.”
  • Open the page and its sources. Check for October 22, Mei, 15 minutes, and an unconfirmed venue. The old October 20 date must not appear as the current plan. Leave the page unedited for the next step.
  • Change October 22 to October 24 in 02-update.md. Wenlan follows the vault in the background and checks about every 30 seconds, so wait a moment for the change to be picked up. Ask Claude to read that Page’s sources again and update the same Page ID. Check that the body now says October 24 and still links to the three notes. Picking up the change alone does not rewrite the page.
Connect Wenlan before the exercise
npx -y wenlan setup
# then, inside Claude Code:
/plugin marketplace add wenlan-app/wenlan
/plugin install wenlan@7xuanlu-wenlan

View a different project’s recorded citation and revision walkthrough (Tally)

Turn your notes into a project brief you can keep updating

Start with your existing notes and create your first cited project brief in Wenlan. Follow the exercise above to update the same page when a source changes.

Inspect a citation and a proposed revision in Wenlan

These are real Wenlan app recordings using Tally, a demonstration invoicing project. Enlarge the screens to follow a source reference and inspect a proposed page revision.

1. Follow the SQLite claim back to its source

The wiki says Tally uses SQLite for a single-user app. The open citation shows the source titled ‘SQLite for Single-User App’, its summary, and an ‘Open memory’ action. Compare the sentence with that source before reusing the decision.

Recorded Wenlan Tally wiki with the SQLite citation open, showing the source summary and Open memory action.

Scroll or swipe to explore the enlarged image.

Open original
Tally demo recording: wiki page and source popover. A source link makes a claim inspectable; you still need to check whether the source supports it.

2. Read the proposed change before approving it

The Project notes revision removes the undecided database wording and proposes a SQLite decision. Added and removed text, an earlier version, and Skip / Approve controls are visible. Check the revised wording and its sources before choosing what to keep.

Recorded Wenlan Project notes revision with added and removed text, an earlier version, and Skip and Approve controls.

Scroll or swipe to explore the enlarged image.

Open original
Tally demo recording: a proposed page revision. This frame does not show an approved result or prove that every changed sentence is correct.

FAQ

How do I find relevant Obsidian notes without knowing their filenames?+
Give Claude Code a project, a question, and a starting folder. Ask it to find and read relevant notes before answering, cite each dated statement, separate superseded decisions from current ones, and report the folders searched. Check the original notes; a filename or a new save date is not proof of a new decision.
How do I connect Claude Code to my Obsidian vault?+
Open a terminal in the vault folder and run claude, or run claude --add-dir with the vault path from another project. No plugin is needed for Claude Code to read and edit notes.
Does Obsidian have a Claude Code plugin?+
Not an official one. Community plugins such as Claudian run Claude Code inside Obsidian, and obsidian-claude-ide shares your active note with Claude Code in a terminal.
Do I need an MCP server to use Claude Code with Obsidian?+
No. Claude Code can read files directly. A normal Claude Desktop chat needs MCP for vault tools, while its Code tab also supports Local folder access. MCP can also share the same vault tools across clients.
Can Claude Code see Obsidian links and backlinks?+
It can read [[wikilinks]] in the text. To list backlinks or use Obsidian search, turn on the Obsidian CLI and install the Obsidian skills so Claude Code knows how to call it.
Is it safe to let Claude Code edit my vault?+
Back up the vault with git or Obsidian Sync first, start with one folder, and keep AI-written notes separate. Claude Code sends the text it reads to your configured model provider.

Share this guide