Barside
Download
Barside/Content/Intelligence · AI search

Intelligence · AI search

How to connect an Obsidian vault to Claude Desktop with an MCP server

We found no official Obsidian MCP server for Claude Desktop. The documented route is the MCP project's Filesystem server: add it to claude_desktop_config.json with your vault folder as an allowed directory, restart Claude Desktop, and approve each file action Claude asks for.

Feature guideUpdated 16 min read

To use an Obsidian vault with an MCP server in Claude Desktop, you add a server entry to Claude Desktop's claude_desktop_config.json file and give it your vault folder as an allowed directory. We found no official Obsidian MCP server, so the documented route is the Filesystem server from the MCP project, which works with the Markdown files in the folders you name. Restart Claude Desktop, and Claude can list, read and write the notes in that vault, asking for your approval before each file action.

Everything here about Claude Desktop, MCP and Obsidian comes from the MCP project's own guide, the Filesystem server's README, Anthropic's help center and Obsidian's help pages, as we read them on November 6, 2026. We ran no tests and took no screenshots, so open the linked page before you rely on a detail. We make Barside, a free desktop app for Windows, Linux and Mac, and the second half of this guide shows its own connection to Claude Desktop, which reaches the notes in Barside's library.

Is there an official Obsidian MCP server for Claude Desktop?

For an Obsidian MCP server in Claude Desktop, we found no official option from Obsidian. The Obsidian help pages list no MCP feature, and the closest official tool is the Obsidian CLI, which controls Obsidian from a terminal for scripting and automation. It needs the Obsidian 1.12 installer (its install steps say 1.12.7 or later), the app has to be running, and we found no mention of MCP on its page.

A vault doesn't need an Obsidian-specific server to be readable. Obsidian's page on how it stores data says "Obsidian stores your notes as Markdown-formatted plain text files in a vault", and a vault is a folder on your computer. The same page says "Obsidian automatically refreshes your vault to keep up with any external changes," so a note that Claude writes into the folder appears in Obsidian. That is why a general file server works on a vault.

Community servers built for Obsidian are the other route, and each works differently, so read its own README before you install it. For example, mcp-obsidian, a community project on GitHub, describes itself as an MCP server that talks to Obsidian through the Local REST API community plugin, so that plugin has to be running, and you copy an API key from the plugin's settings into the server's configuration. Its README lists seven tools, from listing and reading files to searching, patching and appending, plus delete_file, which removes a file or directory from your vault. Check that a project is still maintained, too: the listing for the MCP Tools plugin in Obsidian's community directory says it has been archived and is no longer available.

Whichever server you choose, the MCP project's guide gives one warning about folder access, and it applies to every vault:

Connect your Obsidian vault to Claude Desktop with MCP, step by step

To connect an Obsidian vault to Claude Desktop with MCP, follow the MCP project's guide to connecting local MCP servers and put your vault folder where its example uses the Desktop and Downloads folders. The guide says Claude Desktop is available for macOS, Windows and Linux, and its Filesystem server runs with Node.js.

  1. Install Node.js. The guide says the Filesystem server and many other MCP servers need it. Run node --version in a terminal, and if nothing comes back, install the LTS version from the Node.js website, which the guide recommends for stability.
  2. Note your vault's full path. The guide's troubleshooting says the paths in the file must be valid and absolute. For example, a made-up vault could sit at C:\Users\maya\Documents\Research Vault on Windows or /Users/maya/Documents/Research Vault on a Mac.
  3. Open the configuration file. Open the Claude menu in your system's menu bar, which is separate from the settings inside the Claude window, and choose Settings…. In the Developer tab, click Edit Config. The guide says this creates the file if it doesn't exist yet.
  4. Add the Filesystem server. Add an entry under mcpServers that starts @modelcontextprotocol/server-filesystem with your vault path, as the next section shows. The guide's example replaces the whole file, so if yours already lists other servers, add the new entry beside them inside the same mcpServers object (general advice).
  5. Restart Claude Desktop. Quit it completely and open it again. The guide says the app has to restart to load the new configuration and start the server.
  6. Check the tools. Click Add files, connectors, and more at the bottom left of the message box, point to Connectors and choose Manage connectors. Pick your server to see its tools.
  7. Ask, then approve. Ask Claude about your vault, such as which notes sit in a folder. The guide says Claude asks for your approval before each file system operation, and you can deny any request.

If the server doesn't show up, the guide's checklist is short: restart Claude Desktop completely, check the file's JSON syntax, make sure every path is absolute and valid, read the logs, and run the same npx command by hand in a terminal to see its errors. In the logs folder, mcp.log covers connections and failures, and a file named mcp-server-SERVERNAME.log holds each server's own output.

Where claude_desktop_config.json lives, and what an entry looks like

The official Claude Desktop MCP configuration in the MCP project's 2026 guide is one file, claude_desktop_config.json, and Claude Desktop starts every server listed in it when the app launches. Anthropic's help center describes a second way to add servers, desktop extensions, which a later section covers. The file and the MCP logs sit in these places:

Systemclaude_desktop_config.jsonMCP logs
Windows%APPDATA%\Claude\claude_desktop_config.json%APPDATA%\Claude\logs
Mac~/Library/Application Support/Claude/claude_desktop_config.json~/Library/Logs/Claude
Linux~/.config/Claude/claude_desktop_config.json~/.config/Claude/logs

An entry has three parts. The name under mcpServers is a label of your choice that appears in Claude Desktop. command is the program that starts the server, and args holds its arguments, ending with the folders the server may use. The guide's example runs npx, Node.js's package runner, with -y to confirm the package install without a prompt.

These entries are examples with a made-up vault called Research Vault. Change the path to your own.

  • Mac: {"mcpServers": {"obsidian-vault": {"command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/maya/Documents/Research Vault"]}}}
  • Linux: the same entry with a path such as /home/maya/Documents/Research Vault.
  • Windows: {"mcpServers": {"obsidian-vault": {"command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", "C:\\Users\\maya\\Documents\\Research Vault"]}}}. JSON needs each backslash doubled, as the guide's own Windows example shows.

To give Claude more than one vault, add each folder to the end of args; the guide says you can add directories as needed. On Windows, the Filesystem server's README on GitHub also shows a variant that starts the server through cmd, with "command": "cmd" and /c as the first item in args, before npx. The MCP guide adds a fix for one Windows error: if a server's log shows ENOENT with ${APPDATA} in a path, put the expanded value of %APPDATA% under an env key in the entry, and make sure npm is installed globally.

Use Barside inside Claude Desktop or ChatGPT · Open the video

What the Filesystem server can read and change in your vault

Once the Filesystem server points at a vault folder, Claude can work with any file inside it. That includes attachments, subfolders and the vault's .obsidian folder, which Obsidian's help says holds preferences for that vault, such as hotkeys, themes and community plugins. The server's README lists 15 tools, plus read_file, a deprecated alias of read_text_file, and this table groups the 15 by what they do.

What Claude can doTools in the READMEChanges files
Read notes and attachmentsread_text_file, read_multiple_files, read_media_fileNo
Look around the vaultlist_directory, list_directory_with_sizes, directory_tree, get_file_info, list_allowed_directoriesNo
Find filessearch_files, which matches names and paths with a glob patternNo
Write and edit noteswrite_file (creates or overwrites), append_file, edit_file (find-and-replace edits with a dry run and a diff)Yes
Organizecreate_directory, move_file (move or rename), copy_fileYes

The README marks nine of the 15 as read-only and six as able to change files, and it gives write_file, edit_file and move_file the destructive hint. None of the tools has delete or remove in its name, though the README's feature list includes "Create/list/delete directories". Even so, write_file and edit_file overwrite files in place, and the README says that overwrite is not crash-atomic, so a crash can leave a file partly written. It suggests a dry run before edit_file applies its changes.

Search works on names. The guide's overview mentions searching for files by name or content, while the README's entry for search_files says it finds files and directories by name, with a glob over their paths, and never reads or searches inside files. General advice: name the folder or the note you mean, so Claude reads a few files instead of walking the whole vault.

To let Claude read your vault and change nothing, the README offers a --read-only flag that serves only the tools that cannot change the filesystem; calls to the write tools then fail as unknown tools. The README says the flag may appear anywhere among the arguments, so an entry's args could look like this example: ["-y", "@modelcontextprotocol/server-filesystem", "--read-only", "/Users/maya/Documents/Research Vault"]. It covers every folder that server can reach. To keep one vault writable and another read-only, the README suggests two servers, backed by your system's own file permissions.

A few more details from the README matter for vaults:

  • Links to other folders. Paths are resolved before they are checked, so a symbolic link that points outside the allowed folders is refused. If your vault links in a folder from elsewhere, add that folder to args as well.
  • Large vaults. search_files and directory_tree stop after 100,000 entries, and each directory read in them times out after 15 seconds.
  • A backup first. General advice: back up a vault you care about before you approve the first write, because Obsidian picks up outside changes on its own.

Desktop extensions or the JSON file: Claude Desktop's MCP options in 2026

The official docs in 2026 describe two ways to add an MCP server to Claude Desktop: desktop extensions in Anthropic's help center, and the claude_desktop_config.json file covered above, in the MCP project's guide. Anthropic's help article on local MCP servers in Claude Desktop calls desktop extensions single-click installable packages for local MCP servers, offered in place of configuring JSON files and dependencies by hand.

  1. To install from the directory, open Settings → Desktop app, click Manage next to Extensions, and choose Browse extensions. Click Install and enter any settings the extension asks for, such as an API key.
  2. To install a custom extension, go to Advanced settings, find the Extension Developer section, click Install Extension… and pick the .mcpb file.

The article says Claude Desktop includes a built-in Node.js environment for extensions, so you don't install Node.js for them, and that extensions can also run Python and binary servers. Settings an extension marks as sensitive are encrypted with your system's secure store: the Keychain on a Mac, Credential Manager on Windows, or the distribution's keychain manager on Linux. Owners on Team and Enterprise plans can turn public extensions on or off and upload custom extensions for their team.

Desktop extensionclaude_desktop_config.json
How you add itBrowse extensions, or a .mcpb fileEdit the file, then restart
Node.jsBuilt into Claude DesktopThe Filesystem example uses npx, so you install Node.js
API keys and other settingsEntered in the app; sensitive ones in your system's secure storeTyped into the file, for example under env
Documented byAnthropic's help centerThe MCP project's guide

That help article doesn't mention claude_desktop_config.json, and we found no statement in it about hand-edited configurations going away. The MCP project's guide still documents the file and the Edit Config button as of November 2026. The article also refers to an older Settings layout, so the labels in your version of Claude Desktop may differ a little from either page.

The Barside route: Claude Desktop with your Barside notes

Barside notes are not a Markdown vault, so this is a different setup from pointing Claude at Obsidian files. Barside keeps your library in its data folder on your computer, as one library file for notes and settings plus a media folder for images, video and audio. You can export everything as one ZIP backup, and there is no export to a folder of Markdown files. In place of a file server, Barside has its own connection: Use Barside in your AI app gives Claude Desktop, ChatGPT, Cursor and other MCP apps tools for your library, in the workspaces you choose.

  1. Download Barside for Windows, Linux or Mac, and install Claude Desktop.
  2. In Barside, open Settings and go to Use Barside in your AI app. A quicker route is to press Alt+Shift+Space in any app and type mcp in the search bar.
  3. Choose Add to Claude Desktop. Barside makes a connection for every workspace, with permission to read and add.
  4. To share fewer workspaces, open More apps and options, pick the connection that Add to Claude Desktop made, and choose its workspaces in its Permissions tab. New connection makes a separate connection, and new connections start read-only.
  5. Open Claude Desktop and ask about your notes. If Barside's tools don't show up, the AI connections page has troubleshooting steps.

If your notes live in Obsidian today and you want them in Barside, open Settings & backups, choose Import next to Import notes, then Obsidian and Choose vault folder. Links, embedded images, checklists and front matter come along, and your vault stays as it was. The import makes copies, so the vault and Barside stop being the same files, and up to 5,000 notes and 1 GB of files go in at a time. The guide to moving from Obsidian to Barside covers the details.

What Claude can use through Barside

  • Notes. search_notes and get_note search and read note text in the shared workspaces. Claude reads linked notes as the titles they show, the columns and cards of kanban boards, and the words in drawings.
  • Tasks and reminders. list_tasks lists your checklist tasks. With permission, add_task adds one and update_task changes its text, done state, due date or reminder, and the change shows on Barside's task board.
  • Bookmarks. Claude can list your bookmarks, and add them when you allow it.
  • Reading. list_reading returns the articles you saved with their highlights, read-only.
  • Ready-made prompts. Plan my day and Weekly review start from your tasks, and Meeting follow-up turns a meeting note into decisions and action items, then asks before it adds any task.

What the connection never touches

  • Nothing is deleted. No AI connection deletes anything in Barside. A connection you make yourself starts read-only, and adding needs the permission Allow adding and updating notes, bookmarks, tasks and reminders.
  • Only the workspaces you share. Claude sees nothing outside the workspaces a connection covers.
  • Some things are never shared. The password vault, the Barside assistant's memory and Spaces stay out of every connection. The account labels on bookmarks reach an AI app only when you turn that permission on.
  • Claude does the thinking. Barside has no AI of its own here, and your Claude plan applies to what Claude Desktop uses.

These are made-up examples with made-up people, to show how each route fits a job:

  • Example: Lena, a PhD student, shares only her Thesis workspace through a read-only Barside connection and asks Claude Desktop to "find my notes on sampling bias and list the sources each one cites." Claude uses search_notes and get_note, and nothing in her library changes.
  • Example: Omar, a freelance developer, keeps code snippets in an Obsidian vault that the Filesystem server reaches with --read-only, and his client tasks in Barside. He asks Claude which client tasks are due this week, and Claude answers from list_tasks.

Privacy: what Claude sees on each route

With the Filesystem server, the guide says the server runs with your user account's permissions on your computer, limited to the folders you list. With Barside, your library lives on your computer too, and the privacy guide explains where. Through Barside's connection, the notes Claude reads from the workspaces you share go to Anthropic as part of your conversation, and Anthropic's terms for your plan apply. General advice for either route: if a folder or workspace holds client work you can't send to an AI company, leave it out of args or out of the connection.

The AI connections section of the privacy guide sets out the limits of each connection. Barside also counts which features are used: it sends barside.space the names of the features used that day, with the system and the Barside version, never notes, files or who you are. It's on by default, and a switch in Settings turns it off.

Which setup fits you

Pick by what your notes are made of and how much you want Claude to change.

RouteWhat Claude reachesWhat it can changeSetup
Filesystem server on a vaultEvery file in the folders you listWrites, edits, moves and copies files unless you add --read-only; asks before each actionNode.js, an entry in claude_desktop_config.json, a restart
A community Obsidian server, such as mcp-obsidianThe vault, through the Local REST API pluginPer its README, patching, appending and deleting filesObsidian running with the plugin, and an API key in the configuration
Barside's connectionNotes, tasks, bookmarks and Reading in the workspaces you shareReads, and adds when you allow it; never deletesAdd to Claude Desktop in Barside's settings

Obsidian's plain files are a real strength here: Obsidian's help says you can use other text editors and file managers on your notes, and that is exactly what an MCP file server does. If you want links, tasks, Reading and an AI that uses your own account in one app, the Obsidian alternative guide compares the two fairly. For questions answered only from your notes, with citations, see AI second brain apps that answer only from your notes, and for what else the desktop app adds, read Claude Desktop app features in 2026.

Works well with

Barside's own AI search that cites its sources answers questions from your library inside Barside, and the AI assistant edits notes in place with Undo. Both use the AI you connect in Settings → AI.

FAQ

Questions and answers

Is there an official Obsidian MCP server for Claude Desktop?

We found no official one. Obsidian's help pages list no MCP feature as of November 2026, and the closest official tool is the Obsidian CLI, which controls Obsidian from a terminal. To give Claude Desktop your vault, you can point the MCP project's Filesystem server at the vault folder, or use a community server such as mcp-obsidian, as its own README describes.

Where is claude_desktop_config.json on Windows, Mac and Linux?

The MCP project's guide gives %APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on a Mac and ~/.config/Claude/claude_desktop_config.json on Linux. In Claude Desktop, Settings… in the Claude menu, then the Developer tab and Edit Config, opens the file and creates it if it does not exist yet.

Can Claude delete notes in my Obsidian vault through the Filesystem server?

None of the Filesystem server's 15 tools has delete or remove in its name, but write_file and edit_file overwrite files in place and move_file moves them. Claude asks for your approval before each file action, and the --read-only flag serves only the tools that cannot change files. Community servers differ: the mcp-obsidian README lists a delete_file tool.

Do I need Node.js to add an MCP server to Claude Desktop?

For the Filesystem server set up by hand, yes: the MCP project's guide says it and many other MCP servers need Node.js, and its example starts the server with npx. Desktop extensions are different. Anthropic's help center says Claude Desktop includes a built-in Node.js environment for them, so you do not install Node.js.

Can I point the Filesystem server at my Barside notes?

Barside has its own connection for that. Barside notes are not Markdown files: Barside keeps one library file and a media folder in its data folder. To let Claude Desktop read them, open Settings → Use Barside in your AI app and choose Add to Claude Desktop. See AI search that cites its sources for asking your notes inside Barside too.

What can Claude Desktop see through Barside's connection?

Only the workspaces the connection covers. Claude can search and read notes with search_notes and get_note, list tasks, bookmarks and Reading, and add notes, tasks, bookmarks and reminders when you allow it. No AI connection deletes anything, connections you make yourself start read-only, and the password vault, the assistant's memory and Spaces are never shared.

Is Barside free?

Yes. Barside is free on Windows, Linux and Mac. When you work through Claude Desktop, your Claude plan covers what Claude uses. Barside Plus is optional, at US$20 a month or US$200 a year plus sales tax, for cloud sync between computers, encrypted cloud backup and cloud agents.

Sources

Where the facts come from

Checked on November 9, 2026. Products change: if something here is out of date, tell us at support@barside.space.

  1. Model Context Protocol: Connect to local MCP servers
  2. Filesystem MCP Server (modelcontextprotocol/servers on GitHub)
  3. Claude Help Center: Getting Started with Local MCP Servers on Claude Desktop
  4. Obsidian Help
  5. Obsidian Help: Obsidian CLI
  6. Obsidian Help: How Obsidian stores data
  7. Obsidian community plugins: MCP Tools
  8. mcp-obsidian on GitHub (README)