Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Cool Workflow

by coo1whiteversion 0.1.97i★ –iRuns on your computer
Registry nameio.github.coo1white/cool-workflow

Install

Overview

Description from the maker (original English)

Signed, cited, replayable workflows for Claude, Codex, Gemini, DeepSeek, and other agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "cool-workflow": {
      "command": "npx",
      "args": [
        "-y",
        "cool-workflow"
      ]
    }
  }
}

Run this in your terminal

claude mcp add cool-workflow -- npx -y cool-workflow

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "cool-workflow": {
      "command": "npx",
      "args": [
        "-y",
        "cool-workflow"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "cool-workflow": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "cool-workflow"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account coo1white, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32583 servers in this category
  • Published to the registry more recently than 15% of the other 32583 servers in this category
  • Basic checks equal to or better than 100% of the other 32583 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Cool Workflow safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.97) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

sync. labs

by synchronicity-labs

Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Get a saved report from your AI agent, with every claim tied to a line of code — not a chat answer you lose.

What is this?

Cool Workflow (cw) is a small command-line tool that turns your AI coding agent's chat answer — easy to lose, hard to check — into a saved report. Point it at a repo, or any folder of docs, and:

  • It plans the work. Your question becomes a set of small tasks.
  • Your agent does the work. CW never runs a model itself — your own agent reads and thinks.
  • It writes a checked report. Every claim points to a real place in your code, like file.ts:42. A result with no evidence stops instead of passing through.

The model is fuel. CW is the black-box recorder, the dashboard, and the gearbox — never the engine.

It never calls a model API, never holds your keys, and never uploads your code.

Before you start

You need two things, and one more for real runs:

  1. A terminal. On macOS: Terminal. On Linux: any. On Windows: install WSL (run wsl --install in PowerShell, then open "Ubuntu" from the Start menu) and type every command below in that Ubuntu window.
  2. Node.js v22.13 or newer. Check with node -v. If it is missing or older, get it from nodejs.org (take the LTS one).
  3. An AI coding agent, for real runs — for one, Claude Code or Codex (see Works with your agent). Not needed for the demo in step 1 of the Quick Start.

Install

npm install -g cool-workflow

cw version

cw version prints the version number when the install worked.

Install trouble?

What you seeWhat to do
EACCES: permission deniedDo not use sudo. Put Node in your home folder with nvm, then run the install again.
cw: command not foundClose the terminal and open a new one. If it is still not found, npm prefix -g gives the folder; its bin folder needs to be on your PATH.
Unsupported engine or a Node errorYour Node is older than v22.13: update it (node -v to check).

Or install with Homebrew

brew tap coo1white/cool-workflow https://github.com/coo1white/cool-workflow

brew install coo1white/cool-workflow/cool-workflow cw version

Upgrade later with brew update && brew upgrade cool-workflow.

You need: Node.js v22.13 or newer. No agent yet? Step 1 below still works — CW never runs a model itself.

Runs on: Linux, macOS and Windows through WSL. Native Windows is not yet supported: CI runs it to measure what still fails, and that work is going on.

Works with your agent

AgentFlagStatusGet it
Claude Code-claude✅ worksinstall
Codex CLI-codex✅ worksinstall
Muse Code-muse✅ works—
OpenCode-opencode✅ worksinstall
Gemini-gemini✅ through opencodeinstall OpenCode
DeepSeek-deepseek✅ through opencode or an HTTP endpointinstall OpenCode
GitHub Copilot CLI-copilot🧪 betainstall
Antigravity-antigravity🧪 betainstall
Grok-grok✅ works (add -grok)install
Cursor—⬜ not yet
Aider—⬜ not yet
Qwen Code—⬜ not yet
Kimi—⬜ not yet

🧪 beta: CW has a wrapper and an offline test for it, but no real login has passed cw doctor --conformance yet, and cw never picks it by itself: add its flag.

Log in to your agent once on its own (run it, for one claude, and follow its steps) before you use it with CW: CW uses your agent as it is set up, and never asks for your keys.

Not sure what you have? cw doctor checks your setup and cw fix prints the commands that put it right.

Quick Start

1 · See it work — 30 seconds, no agent needed
cw demo tamper

→ builds a real signed ledger, forges it three ways, catches all three offline

→ VERDICT: tamper-evidence holds ✓

2 · Ask a question about your code — one command
cw -q "How does auth work end-to-end here?"

CW uses the current repo and the first agent it finds on your PATH. Want a specific agent? Add a flag from the table above, such as -claude.

A full review takes about 4 minutes on a real repo (14 workers; the Map and Assess stages run at the same time). One focused question? Add --fast: 6 workers in place of 14, the same cited answer for fewer agent calls.

3 · Open the report

The report opens in your browser by itself when the run ends. It starts with the answer, then the evidence behind it. Later, open it again with:

cw report --open

Want to see one first? A real run's Workbench and report, rebuilt on every push: [coo1white.github.io/cool-workflow](https://coo1white.github.io/cool-workflow/) (the report is at /report.html).

4 · Keep proof that your tests passed

An agent that says "all tests pass" has only said it. Run the tests through CW and keep a receipt:

cw check -- npm test

→ ✓ passed: npm test (exit 0 at 1a2b3c4) — receipt rc-…. Cite it as receipt:rc-…

CW runs your command (never a model) and saves what happened: the commit, the exit code, a digest of the output. A result that cites receipt:rc-… is checked again before it counts: a failed run, a missing receipt, or code that changed since the run is turned down, with the one command to fix it. cw check list shows your receipts.

These steps are the core path. Everything else is kept working, not grown.

Words you will see

WordWhat it means
agentThe AI coding tool on your machine (Claude Code, Codex, …) that does the reading and thinking. CW gives it small tasks.
runOne question, from start to report. Each run has an id, and its files are kept in .cw/runs/ / in your project.
reportThe answer, with the evidence for each claim (file.ts:42). Kept as report.md, and opened in your browser.
evidenceA pointer to a real line of code. A claim without it is not let through.
receiptA record, from cw check, that a command (for one, your tests) truly ran and how it ended.
resumeGoing on with a run that stopped: cw --resume --run .

Can You Trust the Report?

CW does not run the model — it keeps the books. Your agent signs its findings (ed25519), and cw report verify-bundle checks — offline, with only the public key — that every signed finding is in the report unaltered. CW holds no private key: the agent signs, CW only verifies. This proves the signed findings reached you unaltered — not that nothing else was added, and not that none were left out. See the [Trust Model](plugins/cool-workflow/docs/trust-model.md).

Troubleshooting

ProblemFix
No agent foundcw doctor — shows which agents are on your machine
status: blockedSet CW_AGENT_COMMAND=builtin:claude or pass -claude
claude: command not foundInstall Claude Code and run again
Where is my report? /.cw/runs/ /report.md, or run cw report --open
Missing required input: questionAdd -q " "
Run stopped before the endFix the cause, then cw --resume --run takes it to the end; a worker that stopped gets fresh tries (inside the project, or add --repo )
... is not a git projectRun it inside the project, or pass --repo
Run was made for The run belongs to another folder (a copied or moved repo): pass --repo , or move it with cw run export and cw run import

Learn more

  • [User Guide](https://github.com/coo1white/cool-workflow/wiki/User-Guide) — your first ten minutes
  • [Why Cool Workflow](https://github.com/coo1white/cool-workflow/wiki/Mental-Model)
  • [How it works](https://github.com/coo1white/cool-workflow/wiki/Architecture)
  • [What you can run](https://github.com/coo1white/cool-workflow/wiki/Workflow-Apps)
  • [From your editor](https://github.com/coo1white/cool-workflow/wiki/MCP-And-Manifests#from-your-editor)
  • [Trust & Audit](https://github.com/coo1white/cool-workflow/wiki/Trust-And-Audit)
  • [Repo Map](https://github.com/coo1white/cool-workflow/wiki/Repo-Map)
  • [Wiki home](https://github.com/coo1white/cool-workflow/wiki)
  • [Contributing](.github/CONTRIBUTING.md) — to change CW itself: where to start for each job, the rules, and how to report a security problem

CW dogfoods its own release: every cut runs release-cut against this repo.

License

BSD-2-Clause. Built by COOLWHITE LLC.

Ask PopNx