pickfit

BrowseMCP servers

文件操作 MCP Server(加密软件环境明文读写)

MCP server that reads and writes plaintext via Node.js fs for encrypted-disk environments.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Runtimes: Node.js v20+
  1. Install MCP server globally via npm

    npm install -g mcp-read-file-server

Add it to your agent

claude mcp add mcp-read-file-server -- mcp-read-file-server
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "mcp-read-file-server": {
      "command": "mcp-read-file-server",
      "args": []
    }
  }
}

Add mcp-read-file-server as a server command in your MCP client, then ask the client to use its file tools such as read_file.

Linux x86_64

You need first

  • Runtimes: Node.js v20+
  1. global install package

    npm install -g mcp-read-file-server

Add it to your agent

claude mcp add mcp-read-file-server -- mcp-read-file-server
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "mcp-read-file-server": {
      "command": "mcp-read-file-server",
      "args": []
    }
  }
}

Add mcp-read-file-server as a server command in your MCP client, then ask the client to use its file tools such as read_file.

What it does

  • Read encrypted files as plain text
    How to use it
    1. Ask your MCP client to call the read_file tool with path set to <file>.
    2. The tool returns the file's contents as plain text.
    Tested
  • Write files safely in one transaction
    How to use it
    1. Ask your MCP client to call the write_file tool with path set to <file> and content set to <your text>.
    Tested
  • Edit files by replacing exact text
    How to use it
    1. Ask your MCP client to call the edit_file tool with path set to <file>.
    2. Set oldString to the text to replace and newString to <your text>.
    Tested
  • Search file contents in all subfolders
    How to use it
    1. Ask your MCP client to call the search_files tool with path set to <folder> and pattern set to <your text>.
    Tested

How far pickfit got

macOS arm64

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

Linux x86_64

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

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • read a single file as plaintext
  • search file contents recursively
  • edit files with atomic replacement
  • copy files or directories
  • list directory contents

An alternative to AI Agent built-in file tools.

How pickfit tested it

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

macOS arm64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 2.1.5

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

Linux x86_64

An MCP client called one of its tools

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

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

Differences the test machine hit

  • README: npx -y mcp-read-file-server starts the server
    In the test: run server only via MCP stdio probe (python3 ~/.pickfit/mcp_probe.py -- mcp-read-file-server); invoking the binary directly with --help or no args starts the stdio server and waits for input instead of exiting

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.