Ext Ops Panel
Open dashboard
Comparison

Hyper Marketing vs GrowSurf

Hyper Marketing is a plugin bundle for AI coding tools published by hyperfx-ai. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). GrowSurf is an MCP server published by growsurf.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. 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
MarketplaceHyper MarketingGrowSurf
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 21
Stars (GitHub): 107
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.19.24
Downloads/month (npm): 3 609
Downloads/week (npm): 419
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.19.24
Downloads/month (npm): 3 609
Downloads/week (npm): 419
Forks (GitHub): 1
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

Hyper Marketing vs GrowSurf
FactHyper MarketingGrowSurf
Marketplaces that list it22
Stars (GitHub) (differs)107 (better)0 (worse)
Forks (GitHub) (differs)21 (better)1 (worse)
Last release (differs)2026-10-27 (better)2026-10-24 (worse)
Where it runs (differs)Remote server (backend.hyperfx.ai/mcp)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)31Not a bundle
LicenceMITMIT
Repository (differs)github.com/hyperfx-ai/marketing-skillsgithub.com/growsurf/growsurf-mcp
Changes in the last 7 days (differs)12
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 days ago, requires a keyResponded 4 days ago

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

Hyper Marketing

In its own words, on Claude Code: claude-plugins-community:

Connect the Hyper MCP to run marketing end-to-end from Claude — Google, Meta, TikTok, Pinterest, Amazon & LinkedIn ads, organic social, SEO & AI-search research, competitor intel, ad creative, email, and analytics. 30 skills wrapping 100+ integrations and 500+ marketing tools.

GrowSurf

In its own words, on Official MCP Registry:

Build and manage GrowSurf referral and affiliate programs through AI assistants.

How to run each

Hyper Marketing As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install hyper-marketing@claude-community

GrowSurf As a remote MCP server

Claude Code
claude mcp add --transport http growsurf https://mcp.growsurf.com

Requires: GROWSURF_API_KEY (secret)

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

Both endpoints responded at the last daily 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

The marketplaces of Hyper Marketing publish no settings it asks for, so we do not compare settings.

What it can do: Hyper Marketing · What it can do: GrowSurf · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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