pickfit

BrowseMCP servers

VibesPlug Pro v4.5.0: 176-Skill AI Agent Swarm & SaaT Architecture

AI agent swarm plugin with 176 skills and subagents that turns IDEs into autonomous dev studios.

Tested on Linux

Use it

Linux x86_64

  1. Install vibes-plug globally via npm

    npm i -g vibes-plug
Where the README and reality differ
  • README: README advertises v4.5.0 with 176 skills and 42 MCP tools via `vibes mcp`
    What worked: installed version is 4.2.1 with 147 skills and 8 MCP tools; launch the server directly with node /home/sbx/.local/lib/node_modules/vibes-plug/bin/mcp-server.mjs
  • README: `vibes mcp` starts the stdio MCP server (probe via `vibes mcp` timed out with no answer to initialize; direct node launch answers)
    What worked: bypass the `vibes mcp` wrapper and run node bin/mcp-server.mjs directly so the client's piped stdin reaches the server

Check that it works

vibes --version 2>&1

The output should contain “Vibes-Plug CLI (v4.2.1)”.

Add it to your agent

claude mcp add vibes-plug -- node $HOME/.local/lib/node_modules/vibes-plug/bin/mcp-server.mjs
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "vibes-plug": {
      "command": "sh",
      "args": [
        "-c",
        "exec node \"$HOME/.local/lib/node_modules/vibes-plug/bin/mcp-server.mjs\""
      ]
    }
  }
}

Add node <global npm modules>/vibes-plug/bin/mcp-server.mjs as a stdio MCP server in your MCP client, then call its tools such as vibes_list_skills or vibes_swarm.

What it does

  • Run an autonomous zero-to-production workflow
    How to use it
    1. Connect the vibes-plug MCP server to your MCP client.
    2. Call the vibes_swarm tool with a taskDescription such as {"taskDescription":"<your task>"}.
    3. Read the plan the tool returns as text.
    Tested
  • Turn your IDE into an autonomous agent studio
    Not shown working
  • Serve MCP tools over stdio and SSE
    Not tested
  • Automatically fix CI failures
    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.

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 30 Oct 2026
  • Version 4.2.1

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

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.