pickfit

BrowseMCP servers

Obsidian MCP Server

MCP server that lets AI assistants read, write, search and organize an Obsidian vault.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js 20.19 or newer

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. Install packages globally

    npm install -g @smith-and-web/obsidian-mcp-server mcp-remote
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

npm install -g @smith-and-web/obsidian-mcp-server mcp-remote
ls ~/.local/bin/ | grep -i -E "obsidian|mcp-remote|mcp"; which obsidian-mcp-server; which mcp-remote; mcp-remote --help
mkdir -p /home/sbx/work/vault && cat > /home/sbx/work/vault/welcome.md <<'EOF'
---
tags: [demo, test]
title: Welcome
---
# Welcome

This is a sample note with searchable content about pickfit verification.

See also [[other-note]] and #inline-tag.

## Section One

Details under section one.
EOF
cat > /home/sbx/work/vault/other-note.md <<'EOF'
# Other Note

Content linking back to [[welcome]] with unique word zyxwvu123.
EOF
ls -la /home/sbx/work/vault/ && cat /home/sbx/work/vault/welcome.md
VAULT_PATH=/home/sbx/work/vault PORT=3001 obsidian-mcp-server
curl http://localhost:3001/health

Check that it works

ls ~/.local/bin/ | grep -i -E "obsidian|mcp-remote|mcp"; which obsidian-mcp-server; which mcp-remote; mcp-remote --help

The output should contain “Usage: mcp-remote”.

First thing to try

mkdir -p "$HOME"/work/vault && cat > "$HOME"/work/vault/welcome.md <<'EOF'
---
tags: [demo, test]
title: Welcome
---
# Welcome

This is a sample note with searchable content about pickfit verification.

See also [[other-note]] and #inline-tag.

## Section One

Details under section one.
EOF
cat > "$HOME"/work/vault/other-note.md <<'EOF'
# Other Note

Content linking back to [[welcome]] with unique word zyxwvu123.
EOF
ls -la "$HOME"/work/vault/ && cat "$HOME"/work/vault/welcome.md
VAULT_PATH="$HOME"/work/vault PORT=3001 obsidian-mcp-server
curl http://localhost:3001/health

Add it to your agent

claude mcp add obsidian-mcp-server -e VAULT_PATH='<VAULT_PATH>' -- mcp-remote http://127.0.0.1:3001/sse
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "obsidian-mcp-server": {
      "command": "mcp-remote",
      "args": [
        "http://127.0.0.1:3001/sse"
      ],
      "env": {
        "VAULT_PATH": "<VAULT_PATH>"
      }
    }
  }
}

You fill in

  • VAULT_PATH: Path to Obsidian vault (required)

Ask the user for VAULT_PATH; pickfit never had a value, so these are placeholders.

Start the server with VAULT_PATH=<vault folder> PORT=3001 obsidian-mcp-server, then point your MCP client at it with mcp-remote http://127.0.0.1:3001/sse.

What it does

  • Create, read, update and delete notes
    How to use it
    1. Start the server with VAULT_PATH=<vault folder> PORT=3001 obsidian-mcp-server.
    2. Connect your MCP client through mcp-remote http://127.0.0.1:3001/sse.
    3. Ask the assistant to call the read-note tool with a note path such as <note>.md.
    Tested
  • Search your notes by text
    How to use it
    1. Start the server with VAULT_PATH=<vault folder> PORT=3001 obsidian-mcp-server.
    2. Connect your MCP client through mcp-remote http://127.0.0.1:3001/sse.
    3. Ask the assistant to call the search-vault tool with a query of <your text>.
    Tested
  • Manage tags and frontmatter metadata
    How to use it
    1. Start the server with VAULT_PATH=<vault folder> PORT=3001 obsidian-mcp-server.
    2. Connect your MCP client through mcp-remote http://127.0.0.1:3001/sse.
    3. Ask the assistant to call the list-tags tool to see the tags in your vault.
    Tested
  • Search notes by meaning
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 3 of 4 features work
  4. Works offline

Good for

  • read note contents
  • create a new note
  • full-text search vault with context
  • find notes linking to a note
  • list all tags with usage counts

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 1.12.0

An MCP client handshake over stdio listed 31 tools, and a call to read-note returned a result.

Differences the test machine hit

  • README: VAULT_PATH=/path/to/your/vault npx @smith-and-web/obsidian-mcp-server and npx -y mcp-remote http://localhost:3001/sse
    In the test: npm install -g @smith-and-web/obsidian-mcp-server mcp-remote, then run installed obsidian-mcp-server with VAULT_PATH/PORT; stdio clients/probe connect via mcp-remote http://127.0.0.1:PORT/sse
  • README: no --help/--version documented; server starts in foreground
    In the test: obsidian-mcp-server --help starts the SSE server instead of printing help; use mcp-remote --help or the probe handshake to verify

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.