AgentSidekick

Better agent tooling for Google Ads

Integration gap · Measured demandOverall 52.2 / 100 DERConfidence Medium DERCalculated

502 public GitHub issues mention "Google Ads mcp" (checked 2026-11-21) SRC, while 153 indexed products mention Google Ads DER. On the six weighted components it scores 52.2 of 100, confidence Medium, as of 2026-11-21.

Score breakdown

Contribution = weight × component score. The contributions add up to the overall score.

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.2540.00.25 × 40.0 = 10.00Measured
Competition gap0.2017.00.20 × 17.0 = 3.40Measured
Monetisation0.2055.00.20 × 55.0 = 11.00Heuristic
Growth (relative)0.1579.00.15 × 79.0 = 11.85Measured
Feasibility0.1080.00.10 × 80.0 = 8.00Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0052.15 → 52.2

Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.

Confidence: Medium

Rule: Medium when at least 50 GitHub issues mention the integration and at least 10 indexed products mention it; otherwise Low. Nothing is rated High.

What would raise it

  • Medium is the highest level the rules assign. High would need a second, independent demand source (search volume or marketplace installs), which is not connected.

The opportunity

All text in this section is generated by rule from the record. It is a starting point, not research.

Description
Developers are asking for Google Ads access from AI agents more than the current supply of well-maintained tools would suggest.DER
Problem
Agents need to read from and act on Google Ads. Only some of the existing tools are both documented and actively maintained.DER
Target users
Developers and individuals who use Google AdsHEU
Product form
MCP server (optionally bundled as a plugin with skills)HEU
Revenue model
Open source with paid hosting or supportHEU
Complexity
Low to mediumHEU
Competition level
HighDER
Subject
Google Ads (integration)

Evidence for

3 row(s) from opportunity_evidence.

  • Growth (relative)MeasuredDERvalue 115

    115 products launched in the last 90 days versus 18 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.

  • FeasibilityHeuristicHEU

    Google Ads has a public API (documentation linked).

    Source

  • DistributionMeasuredDERvalue 37

    37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.

    /platforms/

Evidence against

3 row(s) from opportunity_evidence.

  • DemandMeasuredDERvalue 502

    502 public GitHub issues contain the phrase "Google Ads mcp" (checked 2026-11-21); that is the 40th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.

    Source

  • Competition gapMeasuredDERvalue 74

    153 indexed products mention Google Ads; 74 of them have a complete record and a repository pushed in the last 180 days.

    /integrations/google-ads/

  • MonetisationHeuristicHEU

    Google Ads is not primarily a paid business product; "marketing" tooling is a category companies commonly pay for. This is a rule of thumb, not revenue data.

Existing products

All Google Ads products

The most notable profiled products mentioning Google Ads (up to 8). 153 indexed in total.

AdLoop

MCP serverby getadloop.comSRC

303 GitHub starspushed 5d agoMIT

mcp-google-ads

MCP serverby cohnenHEU

724 GitHub starspushed 1y agoMIT

Adwarp

MCP serverby adwarp-devSRC

25 GitHub starspushed 10d agoMIT

Where it could be distributed

All platforms

37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.

ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more

Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU

Data coverage

Indexed products
153DER
With a full profile
8+DER
Launches, last 90 days
115 vs 18 in the 90 beforeSRC
Demand measured
SRC
Segment calculated
Score calculated

Risks and counterarguments

  • The vendor may ship (or already ships) an official Google Ads server, which usually becomes the default.
  • Issue mentions measure developer discussion, not willingness to pay.
  • 502 public GitHub issues contain the phrase "Google Ads mcp" (checked 2026-11-21); that is the 40th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.
  • 153 indexed products mention Google Ads; 74 of them have a complete record and a repository pushed in the last 180 days.
  • Google Ads is not primarily a paid business product; "marketing" tooling is a category companies commonly pay for. This is a rule of thumb, not revenue data.

Assumptions

What has to be true for the score to mean anything.

  • Mentions of "Google Ads mcp" in GitHub issues reflect developers wanting Google Ads access from agents.
  • Products that mention the integration in their description or package metadata are the competing supply; ones that do not name it are missed.
  • "Well-maintained" means data completeness ≥ 0.6 and a repository push in the last 180 days.
  • Percentiles compare this integration only with the other integrations tracked, not with the wider market.
  • A platform that documents MCP support can run any MCP server; no pairing has been tested.

How to verify this yourself

  1. Run the demand query on GitHub: https://github.com/search?q=%22Google%20Ads%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 502 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
  2. Check the supply on the Google Ads page and search the official MCP Registry and the vendor's own app directory for an official server.
  3. Download the record with all evidence: /api/dataset/opportunities.json.

All opportunities · Methodology · Report an error

Page data last updated .