Ext Ops Panel
Open dashboard
Comparison

com.pulsemcp/hatchbox vs io.github.clezcoding/awesome-coolify

com.pulsemcp/hatchbox is an MCP server published by pulsemcp.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.clezcoding/awesome-coolify is an MCP server published by clezcoding. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplacecom.pulsemcp/hatchboxio.github.clezcoding/awesome-coolify
Official MCP Registry Listed
Version: 0.1.3
Downloads/month (npm): 189
Downloads/week (npm): 42
Forks (GitHub): 10
Stars (GitHub): 81
Not marked · First seen
Listed
Version: 0.1.2
Downloads/month (npm): 347
Downloads/week (npm): 92
Forks (GitHub): 0
Stars (GitHub): 0
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

com.pulsemcp/hatchbox vs io.github.clezcoding/awesome-coolify
Factcom.pulsemcp/hatchboxio.github.clezcoding/awesome-coolify
Marketplaces that list it11
Stars (GitHub) (differs)81 (better)0 (worse)
Forks (GitHub) (differs)10 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (hatchbox-mcp-server)On your machine (awesome-coolify-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)9, secrets among them: 2Not published
LicenceNot statedNot stated
Repository (differs)github.com/pulsemcp/mcp-serversgithub.com/clezcoding/awesome-coolify
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

com.pulsemcp/hatchbox

In its own words, on Official MCP Registry:

MCP server for Hatchbox Rails hosting — env var inspection, deploys, and process monitoring.

io.github.clezcoding/awesome-coolify

In its own words, on Official MCP Registry:

Coolify 4.1.x MCP server — deploy, diagnose, and manage apps, services, and databases

How to run each

com.pulsemcp/hatchbox As a local MCP server: npm package

Claude Code
claude mcp add --env "HATCHBOX_ACCOUNT_ID=<YOUR_HATCHBOX_ACCOUNT_ID>" --env "HATCHBOX_API_KEY=<YOUR_HATCHBOX_API_KEY>" --env "HATCHBOX_APP_ID=<YOUR_HATCHBOX_APP_ID>" --env "HATCHBOX_DEPLOY_KEY=<YOUR_HATCHBOX_DEPLOY_KEY>" --transport stdio hatchbox -- npx -y hatchbox-mcp-server

Requires: HATCHBOX_ACCOUNT_ID, HATCHBOX_API_KEY (secret), HATCHBOX_APP_ID, HATCHBOX_DEPLOY_KEY (secret)

io.github.clezcoding/awesome-coolify As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio awesome-coolify -- npx -y awesome-coolify-mcp

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.clezcoding/awesome-coolify publish no settings it asks for, so we do not compare settings.

What it can do: com.pulsemcp/hatchbox · What it can do: io.github.clezcoding/awesome-coolify · 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