pickfit

BrowseMCP servers

mcptoon

Zero-dependency Python CLI gateway that manages MCP tools and agent skills across 103+ agents with on-demand schema retrieval.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: python
  1. Install mcptoon via uv tool (isolated equivalent of pip install mcptoon)

    uv tool install mcptoon

Check that it works

mcptoon --version

The output should contain “mcptoon 0.8.34”.

Add it to your agent

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

What it does

  • One-config sync across 103+ agents including Claude Code, Cursor and Codex
    Not shown working
  • Cross-registry search and headless call across 17,000+ MCP servers
    Not shown working
  • Skill management with single resident pointer and symlink-based hub
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 3 features work
  4. Needs the network

Good for

  • manage MCP tools and skills across multiple AI agents
  • reduce context window bloat via on-demand tool schema retrieval
  • discover and install MCP servers via plain-language search
  • call MCP tools headless from terminal

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
  • Needed the network
  • Checked on 2 Nov 2026
  • Version 0.8.34

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

Differences the test machine hit

  • README: pip install mcptoon
    In the test: Used uv tool install mcptoon for isolated install to avoid PEP 668 read-only system

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.