pickfit

BrowseMCP servers

FrameJam

Make videos with a coding agent using styles, then review renders by pointing at frames.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node 22+
  • System packages: ffmpeg
  1. install framejam globally via npm

    npm install -g framejam

Check that it works

framejam --help

The output should contain “Usage:”.

Add it to your agent

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

Add framejam --stdio as an MCP server in your coding agent, then ask the agent to open a review for a video.

What it does

  • Review a video from any tool
    How to use it
    1. Connect your MCP client to framejam --stdio.
    2. Call the open_review tool with a title and the videoPath of your <file>.
    3. Open the review link it returns to leave comments.
    Tested
  • Make videos with a coding agent
    Not shown working
  • Apply a video style picked from examples
    Not shown working
  • Give feedback by clicking on video frames
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • pick a video style instead of describing one
  • comment by clicking a frame spot or dragging a timeline range
  • review a storyboard of one still per shot

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 31 Oct 2026
  • Version 0.1.0

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

Differences the test machine hit

  • README: npx -y framejam install cursor / npx -y framejam --stdio
    In the test: npm install -g framejam provides framejam --stdio on PATH; use framejam --stdio for offline replay instead of npx -y launcher

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.