Ext Ops Panel
Open dashboard
Comparison

AdCopilot vs Hermoso

AdCopilot is an MCP server published by adcopilot.cloud. Marketplaces we read that list it: 1 (Official MCP Registry). Hermoso is an MCP server published by hermoso-ai. 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
MarketplaceAdCopilotHermoso
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.1.458
Downloads/month (npm): 13 689
Downloads/week (npm): 632
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.1.454
Downloads/month (npm): 13 689
Downloads/week (npm): 632
Forks (GitHub): 0
Stars (GitHub): 2
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

AdCopilot vs Hermoso
FactAdCopilotHermoso
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)22
Forks (GitHub)00
Last release (differs)Not published2026-10-27
Where it runs (differs)Remote server (mcp.adcopilot.cloud/mcp)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/atromxintelligence/adcopilot-claude-plugingithub.com/hermoso-ai/hermoso
Changes in the last 7 days (differs)220 or more
First seen (differs)2026-10-232026-10-11
Endpoint at the last check (differs)not checked yetResponded 3 days ago, requires a key

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

AdCopilot

In its own words, on Official MCP Registry:

Google Ads, GA4, Search Console and Tag Manager for AI assistants. Every change is proposed first.

Hermoso

In its own words, on Official MCP Registry:

AI marketing agent and AI ad generator: 1035 tools, usable alone. No markup on models.

How to run each

AdCopilot As a remote MCP server

Claude Code
claude mcp add --transport http adcopilot https://mcp.adcopilot.cloud/mcp

Hermoso

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

Requires: HERMOSO_TOKEN (secret)

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

Only Hermoso 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

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

What it can do: AdCopilot · What it can do: Hermoso · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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