Ext Ops Panel
Open dashboard
Comparison

google-ads-agents vs Google Ads MCP by Markifact

google-ads-agents is a plugin bundle for AI coding tools published by Dilshat Rakhimov. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Google Ads MCP by Markifact is an MCP server published by markifact.com. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
Marketplacegoogle-ads-agentsGoogle Ads MCP by Markifact
Community marketplace arcbaslow/google-ads-agents Not seen in the last pass
Version: 0.6.1
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
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

google-ads-agents vs Google Ads MCP by Markifact
Factgoogle-ads-agentsGoogle Ads MCP by Markifact
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (better)1 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.markifact.com/mcp/google-ads)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)491
LicenceMITMIT
Repository (differs)github.com/arcbaslow/google-ads-agentsgithub.com/markifact/google-ads-mcp
Changes in the last 7 days (differs)24
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

google-ads-agents

In its own words, on Community GitHub marketplaces:

Specialist agents and skills for Google Ads read paths, placement safety, and gated campaign creation. Per-MCC profile support.

Google Ads MCP by Markifact

In its own words, on Official MCP Registry:

Google Ads MCP: reports, search terms, negatives, budgets, campaigns. Approval on every write.

How to run each

google-ads-agents As a Claude Code plugin

Claude Code
/plugin marketplace add arcbaslow/google-ads-agents
/plugin install google-ads-agents@google-ads-agents

Google Ads MCP by Markifact As a remote MCP server

Claude Code
claude mcp add --transport http google-ads https://api.markifact.com/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 Markifact 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: google-ads-agents · What it can do: Google Ads MCP by Markifact · Compare two other plugins

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. 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