Ext Ops Panel
Open dashboard
Comparison

DV360 MCP Server vs Google Ads MCP by AdPlug

DV360 MCP Server is an MCP server published by cesteral. Marketplaces we read that list it: 1 (Official MCP Registry). Google Ads MCP by AdPlug is an MCP server published by danielpopamd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceDV360 MCP ServerGoogle Ads MCP by AdPlug
Official MCP Registry Listed
Version: 1.4.0
Downloads/month (npm): 919
Downloads/week (npm): 91
Forks (GitHub): 5
Stars (GitHub): 8
Not marked · First seen
Listed
Version: 1.0.1
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

DV360 MCP Server vs Google Ads MCP by AdPlug
FactDV360 MCP ServerGoogle Ads MCP by AdPlug
Marketplaces that list it11
Stars (GitHub) (differs)8 (better)0 (worse)
Forks (GitHub) (differs)5 (better)0 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)On your machine (@cesteral/dv360-mcp)Remote server (api.adplug.app/mcp/google-ads)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/cesteral/mcp-open-advertisinggithub.com/danielpopamd/google-ads-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 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

DV360 MCP Server

In its own words, on Official MCP Registry:

DV360 campaign management — writes, targeting, custom bidding, previews, and media uploads

Google Ads MCP by AdPlug

In its own words, on Official MCP Registry:

Google Ads MCP server: 17 tools for reporting, campaigns, keywords, assets. Writes preview first.

How to run each

DV360 MCP Server

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

Google Ads MCP by AdPlug As a remote MCP server

Claude Code
claude mcp add --transport http google-ads-mcp https://api.adplug.app/mcp/google-ads

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

Only Google Ads MCP by AdPlug 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: DV360 MCP Server · What it can do: Google Ads MCP by AdPlug · 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