pickfit

BrowseMCP servers

Taskmaster

A task management system for AI-driven development that parses PRDs into tasks, usable as an MCP server in editors or as a CLI.

Use it

Before you install: known vulnerabilities

pickfit found 15 known high or critical vulnerabilities (16 findings, one per affected package version) in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • npm:@simple-git/argv-parser 1.1.1 simple-git: `VISUAL` editor environment variable is omitted from unsafe editor detection (GHSA-v5rq-49vh-5v5c, critical, fixed in 2.0.1)
  • npm:simple-git 3.36.0 simple-git unsafe-operation guard does not block trailer command configuration (GHSA-x6jw-m9v5-85vh, critical, fixed in 4.0.1)
See 8 more

6 more findings not listed here.

Linux x86_64

You need first

  • Needs the network
  • Keys or accounts: At least one AI provider API key (e.g. Anthropic, OpenAI, Google Gemini, Perplexity, xAI, OpenRouter)

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. npm install -g task-master-ai

    npm install -g task-master-ai
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

npm install -g task-master-ai
task-master --version
mkdir -p /home/sbx/work/proj/.taskmaster/tasks && cat > /home/sbx/work/proj/.taskmaster/tasks/tasks.json <<'EOF'
{
  "master": {
    "tasks": [
      {"id": 1, "title": "Set up project skeleton", "description": "Create repo layout", "details": "", "testStrategy": "", "status": "done", "dependencies": [], "priority": "high", "subtasks": []},
      {"id": 2, "title": "Implement login API", "description": "JWT based login endpoint", "details": "", "testStrategy": "", "status": "pending", "dependencies": [1], "priority": "high", "subtasks": []},
      {"id": 3, "title": "Write docs", "description": "Document the API", "details": "", "testStrategy": "", "status": "pending", "dependencies": [2], "priority": "low", "subtasks": []}
    ],
    "metadata": {"created": "2024-01-01T00:00:00.000Z", "updated": "2024-01-01T00:00:00.000Z", "description": "Tasks for master context"}
  }
}
EOF
cd /home/sbx/work/proj && task-master list

Check that it works

task-master --version

The output should contain “0.43.1”.

First thing to try

mkdir -p "$HOME"/work/proj/.taskmaster/tasks && cat > "$HOME"/work/proj/.taskmaster/tasks/tasks.json <<'EOF'
{
  "master": {
    "tasks": [
      {"id": 1, "title": "Set up project skeleton", "description": "Create repo layout", "details": "", "testStrategy": "", "status": "done", "dependencies": [], "priority": "high", "subtasks": []},
      {"id": 2, "title": "Implement login API", "description": "JWT based login endpoint", "details": "", "testStrategy": "", "status": "pending", "dependencies": [1], "priority": "high", "subtasks": []},
      {"id": 3, "title": "Write docs", "description": "Document the API", "details": "", "testStrategy": "", "status": "pending", "dependencies": [2], "priority": "low", "subtasks": []}
    ],
    "metadata": {"created": "2024-01-01T00:00:00.000Z", "updated": "2024-01-01T00:00:00.000Z", "description": "Tasks for master context"}
  }
}
EOF
cd "$HOME"/work/proj && task-master list

Add it to your agent

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

Inside a project folder that has a .taskmaster directory, run task-master list to see your tasks, or add task-master-ai as an MCP server in your editor.

What it does

  • Get a suggestion for the next task to work on
    How to use it
    1. Keep your tasks in .taskmaster/tasks/tasks.json inside your project folder.
    2. Connect your editor's MCP client to the task-master-ai server.
    3. Call the next_task tool with your project folder as projectRoot, for example {"projectRoot": "<project folder>"}.
    Tested
  • Turn a PRD into a list of tasks
    Not tested
  • Break a task into subtasks
    Not tested
  • Research current information using project context
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • generate tasks from a PRD
  • find the next task to work on
  • research current best practices with project context

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
  • Version 0.43.1

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

Differences the test machine hit

  • README: Launch with npx -y task-master-ai
    In the test: After npm install -g task-master-ai, the task-master-ai binary starts the MCP server directly over stdio (no npx needed)
  • README: MCP server speaks JSON-RPC over stdio
    In the test: The server printed 1 non-JSON-RPC line on stdout; strict MCP clients may complain
  • README: Parse PRD / expand / research via AI chat
    In the test: These tools call an AI provider and need an API key; only non-AI tools (next_task, list) work without one
  • README: An MCP server over stdio writes only JSON-RPC messages to stdout
    In the test: This server wrote 1 other line(s) to stdout during the handshake; strict MCP clients may reject them.

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.