pickfit

BrowseMCP servers

wcode

MCP control plane that helps coding assistants read repos, change code and run checks.

Tested on macOS and Linux

Use it

macOS arm64

  1. download install.sh

    curl -fsSL https://raw.githubusercontent.com/francis-du/wcode/main/install.sh -o /tmp/install.sh && wc -c /tmp/install.sh && head -n 200 /tmp/install.sh
  2. install wcode via script

    sh /tmp/install.sh

Check that it works

wcode --version

The output should contain “wcode 0.9.1”.

First thing to try

wcode --show-config

Add it to your agent

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

Run wcode --show-config to see the current setup, then connect it to your coding assistant as an MCP server.

Linux x86_64

  1. download install script for reading

    curl -fsSL https://raw.githubusercontent.com/francis-du/wcode/main/install.sh -o /tmp/wcode-install.sh && wc -c /tmp/wcode-install.sh && head -c 2000 /tmp/wcode-install.sh
  2. install wcode binary to ~/.local/bin

    sh /tmp/wcode-install.sh

Check that it works

wcode --version

The output should contain “wcode 0.9.1”.

Add it to your agent

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

Run wcode --show-config to see the current setup, then connect it to your coding assistant as an MCP server.

What it does

  • Read repositories and build context for a task
    Not shown working
  • Change code with limited, controlled edits
    Not tested
  • Inspect changes and see their impact
    Not tested
  • Run checks and verify projects
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

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

Good for

  • inspect repository changes
  • manage coding tasks
  • approve access requests
  • see which checks ran against current code

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 0.9.1

An MCP client handshake over stdio listed 85 tools, and a call to workspace_info 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 0.9.1

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

Differences the test machine hit

  • README: curl -fsSL https://raw.githubusercontent.com/francis-du/wcode/main/install.sh | sh
    In the test: installer fetches prebuilt binary tarball plus SHA256SUMS, verifies checksum, then runs it; binary cannot be read before running

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.