Google Ads MCP by Markifact vs MCP Google Ads
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). MCP Google Ads is an MCP server published by Ayo-Fam. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
| Marketplace |   Google Ads MCP by Markifact |  MCP Google Ads |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (PyPI): 85 Downloads/week (PyPI): 20 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
| Fact | Google Ads MCP by Markifact | MCP Google Ads |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.markifact.com/mcp/google-ads) | On your machine (mcp-google-ads-multi) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/markifact/google-ads-mcp | github.com/apexradius/mcp-google-ads |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 15 h ago | no 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
Google Ads MCP by Markifact
Google Ads MCP: reports, search terms, negatives, budgets, campaigns. Approval on every write.
MCP Google Ads
Multi-account Google Ads MCP: campaigns, keywords, search terms, and ad performance.
How to run each
Google Ads MCP by Markifact As a remote MCP server
claude mcp add --transport http google-ads https://api.markifact.com/mcp/google-adsMCP Google Ads As a local MCP server: PyPI package
claude mcp add --env "GOOGLE_ADS_DEVELOPER_TOKEN=<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>" --transport stdio mcp-google-ads -- uvx mcp-google-ads-multiRequires: GOOGLE_ADS_DEVELOPER_TOKEN (secret)
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
The marketplaces of Google Ads MCP by Markifact publish no settings it asks for, so we do not compare settings.
What it can do: Google Ads MCP by Markifact · What it can do: MCP Google Ads · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.