Ext Ops Panel
Open dashboard
Comparison

nitrosend vs GHL Command

nitrosend is a plugin bundle for AI coding tools published by nitrosend. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). GHL Command is an MCP server published by drjerryrelth. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. 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
MarketplacenitrosendGHL Command
Copilot CLI: github/awesome-copilot Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.91.0
Downloads/month (npm): 6 133
Downloads/week (npm): 514
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 3.91.0
Downloads/month (npm): 6 133
Downloads/week (npm): 514
Forks (GitHub): 1
Stars (GitHub): 1
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

nitrosend vs GHL Command
FactnitrosendGHL Command
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 (better)1 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)Not published2026-10-23
Where it runs (differs)Remote server (api.nitrosend.com/mcp)On your machine (@elitedcs/ghl-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITSEE LICENSE IN LICENSE
Repository (differs)github.com/nitrosend/copilotgithub.com/drjerryrelth/ghl-command-feedback
Changes in the last 7 days (differs)29
First seen (differs)2026-10-262026-10-11
Endpoint at the last check (differs)Responded 2 days ago, requires a keyno remote endpoint we check

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

nitrosend

In its own words, on Copilot CLI: github/awesome-copilot:

Prepare and review email campaigns, automation flows, contacts and transactional messages in Nitrosend through its hosted OAuth MCP server. Includes a scoped skill for account selection, consent and live-send review.

GHL Command

In its own words, on Official MCP Registry:

GoHighLevel MCP for Claude: 250 tools, 51 modules, incl. the only programmatic GHL workflow builder

How to run each

nitrosend

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

GHL Command As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ghl-command -- npx -y @elitedcs/ghl-mcp

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

Only nitrosend has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: nitrosend · What it can do: GHL Command · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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