Google Ads MCP by AdPlug

io.github.danielpopamdPublished by GitHub account danielpopamdv1.0.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Hosted Google Ads MCP server that lets an assistant pull spend and conversion reports, research keywords, run GAQL, and preview then apply account changes.

What you can do
  • Check connection status and list accessible accounts with names, currencies and MCC hierarchy
  • Pull cross-account spend overviews, campaign metrics, conversion breakdowns, daily trends and search-term reports
  • Inspect shared negative-keyword lists and research keyword ideas
  • Look up GAQL syntax and reporting-view field references, then run raw GAQL queries
  • Preview and then execute status changes (pause, enable, remove) and negative-keyword additions
When to use it
Useful when you manage Google Ads accounts, including multi-account MCC setups, and want to analyze performance or make small campaign changes from an AI assistant without switching tools. The preview-then-execute flow suits cautious edits to live accounts.
Requirements
A remote hosted endpoint; nothing to install locally. A free AdPlug account with Google Ads connected, and OAuth 2.1 authorization through a browser when adding the connector. Clients without remote HTTP support need an stdio bridge such as mcp-remote via npx. ChatGPT requires a plan that supports custom MCP connectors.
Before you install
The server can change live ad accounts: pause, enable or remove items and add negative keywords, so review every preview before executing. AdPlug holds the Google Ads connection server-side, so account data passes through a third party. Access is granted through OAuth sign-in to AdPlug; no API keys are pasted.

Installation

In SourceWeft

  1. Open Google Ads MCP by AdPlug in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.danielpopamd%2Fgoogle-ads-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "google-ads-by-adplug": {
      "type": "http",
      "url": "https://api.adplug.app/mcp/google-ads"
    }
  }
}

README

[Google Ads MCP by AdPlug]

Google Ads MCP

Connect Google Ads to Claude, ChatGPT, Cursor, and any MCP client.
A hosted, remote Model Context Protocol server by AdPlug.

[Remote MCP server] [Tools] [Auth] [Hosted by AdPlug]

This is a remote, fully hosted server. There is nothing to clone, install, or run. Point your MCP client at the endpoint below and sign in. This repository holds the connection setup and documentation only; the server is operated by AdPlug.

Endpoint

https://api.adplug.app/mcp/google-ads

What it does

Manage and analyze Google Ads in plain language from your AI assistant: pull spend and conversion reports across an entire MCC, research keywords, write raw GAQL, and make safe changes with a preview step before anything is committed. Costs come back formatted with currency symbols, account names are always attached to IDs, and MCC parent accounts are auto-detected so you rarely touch login_customer_id.

Built by a PPC veteran

Hi, I'm Daniel Popa, founder of AdPlug. I have spent 10+ years in performance marketing and managed over $100M in ad budgets, running paid acquisition and conversion optimization for brands including Coca-Cola, Rolex, Boots, British Gas, Europcar, O2, and SeedLegals.

I still run Google Ads and LinkedIn Ads every day, and I built this server because I was tired of switching between the AI I think in and the ad platforms I work in. This is not a generic API wrapper. Every tool exists because I needed it on a live account: a cross-account spend overview in one call, conversion reports that handle GAQL segmentation for you, and a preview step before any change touches a real account. If a workflow felt slow in my own day job, it became a tool.

Questions, feature requests, or PPC war stories? Reach me on LinkedIn or at [email protected].

Quick start

You need a free AdPlug account to authorize the connection. The server uses OAuth 2.1: when you add it, your client opens a browser window where you sign in to AdPlug and connect Google Ads. No API keys or tokens are pasted anywhere.

  1. Create your account at adplug.app and connect Google Ads.
  2. Add the endpoint to your client (pick yours below).
  3. Approve the OAuth prompt. You are connected.

Add it to your client

Claude.ai and Claude Desktop

Settings → Connectors → Add custom connector → paste the name and URL:

FieldValue
NameGoogle Ads MCP
URLhttps://api.adplug.app/mcp/google-ads

A browser window opens to sign in and authorize. Done.

Claude Code (CLI)

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

Then run /mcp inside Claude Code and complete the OAuth login.

ChatGPT

Settings → Connectors → Create (Developer mode / custom connector) → paste the URL https://api.adplug.app/mcp/google-ads and authorize. Requires a ChatGPT plan that supports custom MCP connectors.

Cursor

[Add to Cursor]

Or add it manually to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "adplug-google-ads": {      "url": "https://api.adplug.app/mcp/google-ads"    }  }}

VS Code

bash
code --add-mcp '{"name":"adplug-google-ads","url":"https://api.adplug.app/mcp/google-ads"}'

Any client that needs a stdio bridge (Windsurf, older desktop apps)

Use mcp-remote to bridge the remote server over stdio. It handles the OAuth handshake for you:

json
{  "mcpServers": {    "adplug-google-ads": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://api.adplug.app/mcp/google-ads"]    }  }}

Tools

16 tools, designed as a few flexible tools rather than many narrow ones.

ToolWhat it does
adplug_get_statusCheck whether Google Ads is connected and healthy.
google_ads_list_accountsList all accessible accounts with names, types, currencies, and MCC hierarchy.
google_ads_account_performanceCross-account spend overview in one call (skips MCC managers).
google_ads_campaign_performanceCampaign-level metrics, no GAQL required.
google_ads_conversion_performanceConversion-action breakdowns with segmentation handled for you.
google_ads_daily_trendsDay-by-day metric trends.
google_ads_search_termsSearch-term report, sorted by cost.
google_ads_shared_set_criteriaContents of shared negative-keyword lists.
google_ads_keyword_ideasKeyword research and ideas.
google_ads_gaql_docGAQL syntax reference.
google_ads_reporting_view_docExact field names, types, and filterability for a reporting view.
google_ads_queryRun raw GAQL for custom or advanced queries.
google_ads_preview_mutationPreview a status change (pause / enable / remove) before committing.
google_ads_execute_mutationExecute a previewed change.
google_ads_preview_add_negativesPreview adding negative keywords (campaign-level or shared list).
google_ads_execute_add_negativesExecute the negative-keyword addition.

Authentication

OAuth 2.1 with Dynamic Client Registration. Your client discovers the authorization server from the endpoint, registers itself, and opens a browser for you to sign in to AdPlug and grant access. The connection between AdPlug and Google is held server-side and encrypted; the MCP client never sees a Google token.

Server config (for directory submissions)

json
{  "mcpServers": {    "adplug-google-ads": {      "url": "https://api.adplug.app/mcp/google-ads"    }  }}

Links

More from AdPlug

AdPlug is a marketing control plane that plugs your ad accounts into AI assistants over the Model Context Protocol. This is one of several AdPlug servers:

  • Google Ads MCP (this one): https://api.adplug.app/mcp/google-ads
  • LinkedIn Ads MCP: https://api.adplug.app/mcp/linkedin-ads
  • Unified (Google Ads and LinkedIn Ads in one connector): https://api.adplug.app/mcp

One AdPlug account works across all of them.

License

MIT for the contents of this repository (setup and documentation). The hosted service has its own terms.

Google Ads is a trademark of Google LLC. AdPlug is an independent integration and is not endorsed by or affiliated with Google.

Source: README.md at commit 06665d9

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 21, 2026
  2. v1.0.0Sep 17, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts