io.github.StuMason/coolify vs Cloud DevOps MCP Server
io.github.StuMason/coolify is an MCP server published by StuMason. Marketplaces we read that list it: 1 (Official MCP Registry). Cloud DevOps MCP Server is an MCP server published by alexcgodwin. 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
| Marketplace |  io.github.StuMason/coolify |  Cloud DevOps MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 3.9.0 Downloads/month (npm): 21 742 Downloads/week (npm): 1 935 Forks (GitHub): 93 Stars (GitHub): 611 Not marked · First seen |
Listed Version: 0.14.0 Downloads/month (npm): 2 685 Downloads/week (npm): 173 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
| Fact | io.github.StuMason/coolify | Cloud DevOps MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 611 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 93 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@masonator/coolify-mcp) | On your machine (cloud-devops-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/stumason/coolify-mcp | github.com/alexcgodwin/cloud-devops-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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.StuMason/coolify
46 optimized tools for managing Coolify infrastructure, diagnostics, and docs search
Cloud DevOps MCP Server
Cloud DevOps analysis with guarded Git, infrastructure, cloud and observability operations.
How to run each
io.github.StuMason/coolify As a local MCP server: npm package
claude mcp add --env "COOLIFY_ACCESS_TOKEN=<YOUR_COOLIFY_ACCESS_TOKEN>" --transport stdio coolify -- npx -y @masonator/coolify-mcpRequires: COOLIFY_ACCESS_TOKEN (secret)
Cloud DevOps MCP Server As a local MCP server: npm package
claude mcp add --transport stdio cloud-devops-mcp-server -- npx -y cloud-devops-mcp-serverCommands 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 Cloud DevOps MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: io.github.StuMason/coolify · What it can do: Cloud DevOps MCP Server · 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.