Ext Ops Panel
Open dashboard
Comparison

com.pulsemcp/vercel vs io.github.StuMason/coolify

com.pulsemcp/vercel is an MCP server published by pulsemcp.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.StuMason/coolify is an MCP server published by StuMason. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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/vercelio.github.StuMason/coolify
Official MCP Registry Listed
Version: 0.1.3
Downloads/month (npm): 366
Downloads/week (npm): 56
Forks (GitHub): 10
Stars (GitHub): 81
Not marked · First seen
Listed
Version: 3.9.0
Downloads/month (npm): 21 742
Downloads/week (npm): 1 935
Forks (GitHub): 93
Stars (GitHub): 614
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/vercel vs io.github.StuMason/coolify
Factcom.pulsemcp/vercelio.github.StuMason/coolify
Marketplaces that list it11
Stars (GitHub) (differs)81 (worse)614 (better)
Forks (GitHub) (differs)10 (worse)93 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (vercel-platform-mcp-server)On your machine (@masonator/coolify-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/pulsemcp/mcp-serversgithub.com/stumason/coolify-mcp
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/vercel

In its own words, on Official MCP Registry:

MCP server for Vercel — manage deployments and view build and runtime application logs.

io.github.StuMason/coolify

In its own words, on Official MCP Registry:

46 optimized tools for managing Coolify infrastructure, diagnostics, and docs search

How to run each

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

Claude Code
claude mcp add --env "VERCEL_TOKEN=<YOUR_VERCEL_TOKEN>" --transport stdio vercel -- npx -y vercel-platform-mcp-server

Requires: VERCEL_TOKEN (secret)

io.github.StuMason/coolify As a local MCP server: npm package

Claude Code
claude mcp add --env "COOLIFY_ACCESS_TOKEN=<YOUR_COOLIFY_ACCESS_TOKEN>" --transport stdio coolify -- npx -y @masonator/coolify-mcp

Requires: COOLIFY_ACCESS_TOKEN (secret)

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

Only com.pulsemcp/vercel asks for

  • VERCEL_ENABLED_TOOLGROUPS
  • VERCEL_TEAM_ID
  • VERCEL_TEAM_SLUG
  • VERCEL_TOKEN (secret)

Only io.github.StuMason/coolify asks for

  • COOLIFY_ACCESS_TOKEN (secret)
  • COOLIFY_BASE_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: com.pulsemcp/vercel · What it can do: io.github.StuMason/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