pickfit

BrowseMCP servers

Model Context Protocol servers

A collection of reference MCP server implementations (filesystem, git, fetch, memory, time and others) that demonstrate MCP features and SDK usage.

Tested on Linux

Use it

Linux x86_64

  1. uv tool install mcp-server-fetch and mcp-server-git

    uv tool install mcp-server-fetch && uv tool install mcp-server-git
  2. npm install -g server-memory and server-filesystem

    npm install -g @modelcontextprotocol/server-memory @modelcontextprotocol/server-filesystem

Add it to your agent

claude mcp add servers -- mcp-server-filesystem '<path>'
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "servers": {
      "command": "mcp-server-filesystem",
      "args": [
        "<path>"
      ]
    }
  }
}

Replace <path> with your own path.

Add a server to your MCP client's config, for example mcp-server-filesystem <directory>, then connect the client to see its tools.

What it does

  • Work with files only in folders you allow
    How to use it
    1. Start the server with the folder it may use: mcp-server-filesystem <directory>.
    2. From your MCP client, call list_directory with a path inside that folder.
    Tested
  • Read, search and change Git repositories
    How to use it
    1. Start the server for a repository: mcp-server-git --repository <repo>.
    2. From your MCP client, call git_status with repo_path set to that repository.
    Tested
  • Fetch web pages and convert them for an LLM
    How to use it
    1. Start the server: mcp-server-fetch --ignore-robots-txt --allow-private-ips --no-readability-js.
    2. From your MCP client, call fetch with url set to <your URL>.
    Tested
  • Keep persistent memory as a knowledge graph
    Not shown working

How far pickfit got

Linux x86_64

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

Good for

  • give an LLM access to read, search and manipulate Git repositories
  • fetch and convert web content for LLM use
  • give an LLM controlled file operations

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 15 Nov 2026

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

Differences the test machine hit

  • README: uvx mcp-server-fetch (no flags)
    In the test: To fetch from a local/loopback address the fetch server needs --allow-private-ips (private IPs are refused by default); --no-readability-js avoids starting Node/npm for extraction.
  • README: Launch with npx -y / uvx
    In the test: Installed with uv tool install / npm install -g so the launch commands (mcp-server-fetch, mcp-server-git, mcp-server-memory, mcp-server-filesystem) work offline.

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.