Ext Ops Panel
Open dashboard
Comparison

io.github.PritaS/actionforge vs io.github.coo1white/cool-workflow

io.github.PritaS/actionforge is an MCP server published by PritaS. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.coo1white/cool-workflow is an MCP server published by coo1white. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.PritaS/actionforgeio.github.coo1white/cool-workflow
Official MCP Registry Listed
Version: 1.0.3
Downloads/month (npm): 434
Downloads/week (npm): 82
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.97
Downloads/month (npm): 384
Downloads/week (npm): 133
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.PritaS/actionforge vs io.github.coo1white/cool-workflow
Factio.github.PritaS/actionforgeio.github.coo1white/cool-workflow
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (actionforge-mcp)On your machine (cool-workflow)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/pritas/actionforge-mcpgithub.com/coo1white/cool-workflow
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.PritaS/actionforge

In its own words, on Official MCP Registry:

MCP server for ActionForge: expose your account's tools to Claude and any MCP client.

io.github.coo1white/cool-workflow

In its own words, on Official MCP Registry:

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

How to run each

io.github.PritaS/actionforge As a local MCP server: npm package

Claude Code
claude mcp add --env "ACTIONFORGE_API_KEY=<YOUR_ACTIONFORGE_API_KEY>" --transport stdio actionforge -- npx -y actionforge-mcp

Requires: ACTIONFORGE_API_KEY (secret)

io.github.coo1white/cool-workflow As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio cool-workflow -- npx -y cool-workflow

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.coo1white/cool-workflow publish no settings it asks for, so we do not compare settings.

What it can do: io.github.PritaS/actionforge · What it can do: io.github.coo1white/cool-workflow · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built