pickfit

BrowseMCP servers

Markdown Vault MCP

MCP server to search, read, and write a folder of Markdown notes with hybrid search.

Tested on Linux

Use it

Linux x86_64

  1. install markdown-vault-mcp via uv

    uv tool install "markdown-vault-mcp"

Check that it works

markdown-vault-mcp --help 2>&1

The output should contain “Usage: markdown-vault-mcp”.

Add it to your agent

claude mcp add markdown-vault-mcp -- markdown-vault-mcp serve
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "markdown-vault-mcp": {
      "command": "markdown-vault-mcp",
      "args": [
        "serve"
      ]
    }
  }
}

Set MARKDOWN_VAULT_MCP_SOURCE_DIR to your notes folder, then add markdown-vault-mcp serve as a server in your MCP client.

What it does

  • Search, read and write Markdown notes
    How to use it
    1. Start the server with MARKDOWN_VAULT_MCP_SOURCE_DIR=<your notes folder> markdown-vault-mcp serve.
    2. From your MCP client, call the vault_read tool with the note's path, such as notes/<note>.md.
    Tested
  • Search notes by keyword and meaning
    How to use it
    1. Start the server with MARKDOWN_VAULT_MCP_SOURCE_DIR=<your notes folder> markdown-vault-mcp serve.
    2. Call the vault_search tool with a query and mode set to keyword.
    Tested
  • Track backlinks, outlinks and broken links
    How to use it
    1. Start the server with MARKDOWN_VAULT_MCP_SOURCE_DIR=<your notes folder> markdown-vault-mcp serve.
    2. Call the get_backlinks tool with the note's path to see which notes link to it.
    Tested
  • Commit, sync and review note history with Git
    How to use it
    1. Make your notes folder a Git repository with at least one commit.
    2. Start the server with MARKDOWN_VAULT_MCP_SOURCE_DIR=<your notes folder> markdown-vault-mcp serve.
    3. Call the get_history tool with the note's path to review its history.
    Tested

How far pickfit got

Linux x86_64

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

Good for

  • search a folder of Markdown notes
  • read Markdown notes
  • write back into Markdown notes
  • follow backlinks and outlinks between notes
  • sync notes with git history

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 5.1.0

An MCP client handshake over stdio listed 44 tools, and a call to vault_read returned a result.

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.