Claude Desktop MCP: Filesystem Access for Obsidian

Claude Desktop can connect to local Model Context Protocol (MCP) servers, programs that run on the user’s own machine and expose specific capabilities to the application through a standardized protocol. One of these is the Filesystem Server, which gives Claude controlled access to directories on the computer. Because an Obsidian vault is simply a folder of plain markdown files, the same server can point at a vault and let Claude read and work with those notes.

What the Filesystem Server Does

According to the official MCP user quickstart at https://modelcontextprotocol.io/quickstart/user, the Filesystem Server provides tools for reading file contents and directory structures, creating new files and directories, moving and renaming files, and searching for files by name or content. The documentation lists capabilities including reading text files, reading multiple files at once, retrieving file metadata, writing and editing files, creating directories, moving files, listing directory contents, building a recursive directory tree, and running glob-style searches.

A defining detail of the setup is that every file operation requires explicit approval. The quickstart states that all actions require the user’s approval before execution, so Claude requests confirmation before it reads, writes, or reorganizes anything. The server runs with the user’s own account permissions, which means it can perform any file operations the user could perform manually.

Configuring Access to a Vault

The server is enabled through a JSON configuration file. The quickstart directs users to open Claude Desktop’s Settings, go to the Developer tab, and click Edit Config. That file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows.

The documented configuration starts the Filesystem Server with access to specific directories:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/username/Desktop",
        "/Users/username/Downloads"
      ]
    }
  }
}

The quickstart explains each part: filesystem is a friendly name for the server, command set to npx uses Node.js’s npx tool to run it, -y confirms installation of the server package, and the remaining arguments are the directories the server is allowed to access. To target an Obsidian vault, a user replaces or adds one of those trailing paths with the absolute path to the vault folder. Running the server requires Node.js, which the documentation lists as a prerequisite. After editing the file, Claude Desktop must be fully quit and restarted to load the configuration.

Security and Scope

The documentation includes a direct security note: users should only grant access to directories they are comfortable with Claude reading and modifying. Because access is limited to the exact paths listed in the configuration, the user controls which folders are visible. Listing only a vault path keeps Claude’s reach confined to that directory tree rather than the whole machine.

When the server is connected, Claude Desktop shows an MCP server indicator near the conversation input, and clicking it displays the tools the Filesystem Server makes available. If the indicator does not appear, the quickstart’s troubleshooting section covers checking the JSON syntax, confirming that paths are absolute rather than relative, reviewing the MCP log files, and running the npx command manually to surface errors.

Treated this way, an Obsidian vault becomes a directory Claude can search and edit under the same approval gate as any other folder, without converting the notes out of their plain markdown format.