Google Ads MCP Server

Google Ads is Google's online advertising platform for creating and managing search, display, video, and app advertising campaigns to reach potential customers.

Tools

What is the Google Ads MCP Server?

The Google Ads MCP server gives AI agents structured, permission-aware access to Google Ads through the Model Context Protocol. With 34 pre-built actions, agents can read, create, and update Google Ads data on behalf of authorized users.

Willow ships the Google Ads MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Google Ads is being used by every AI agent in your stack.

Tools

List Accessible Customers

Retrieve all customer IDs accessible to the authenticated user. This is typically the first API call to make when working with Google Ads API, as it returns the list of customer accounts you have access to. Use this to discover which customer IDs you can query.

Get Customer Details

Retrieve detailed information about a specific customer account including descriptive name, currency code, time zone, tracking URL template, and conversion tracking settings. The customer ID from general settings is used by default unless specified.

Search Customers

Execute a custom GAQL (Google Ads Query Language) query against the customer resource. Use this for advanced queries with custom field selection and filtering. Add a LIMIT clause to the query to cap the number of rows returned. Example query: 'SELECT customer.id, customer.descriptive_name FROM customer WHERE customer.status = "ENABLED"'

List Campaigns

List all campaigns in the Google Ads account with optional status filtering. Returns campaign ID, name, status, advertising channel type, and resource name. Use status filter to get only ENABLED, PAUSED, or REMOVED campaigns. Supports pagination for accounts with many campaigns.

Get Campaign

Retrieve detailed information about a specific campaign including all settings: name, status, bidding strategy, budget, targeting settings, advertising channel type, start/end dates, and optimization metrics. Essential for understanding campaign configuration.

Search Campaigns

Execute a custom GAQL query to search campaigns with advanced filtering, sorting, and field selection. Use this for complex queries like finding campaigns by name pattern, budget amount, performance metrics, or multiple conditions. Add a LIMIT clause to the query to cap the number of rows returned. Example: 'SELECT campaign.name, metrics.clicks FROM campaign WHERE metrics.clicks > 1000 ORDER BY metrics.clicks DESC'

Create Campaign

Create a new campaign with specified settings. At minimum, you must provide name, advertising channel type (SEARCH, DISPLAY, VIDEO, SHOPPING, etc.), status, and campaign budget resource name. Optional settings include bidding strategy, start/end dates, and network settings. Returns the created campaign's resource name.

Update Campaign

Update an existing campaign's settings. You can modify name, status, bidding strategy, start/end dates, and other campaign settings. Provide the campaign resource name and only the fields you want to update. The update mask is automatically generated from provided fields.

Mutate Campaigns

Perform batch operations on campaigns - create, update, or remove multiple campaigns in a single request. This is more efficient than individual operations when working with multiple campaigns. Each operation should specify 'create', 'update', or 'remove' with the appropriate campaign data. Operations are executed atomically - all succeed or all fail.

Remove Campaign

Remove (delete) a campaign from the Google Ads account. The campaign will be marked as REMOVED status. Note that removed campaigns cannot be reactivated. Provide the campaign resource name to remove.

1–10 of 34 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your Google Ads MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-google-ads": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/google-ads"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-google-ads": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/google-ads"
    }
  }
}

Claude Code

CLI

claude mcp add willow-google-ads --transport http https://<org>.mcp-s.com/mcp/mcp/google-ads

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/google-ads",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Google Ads

Willow adds the layer Google Ads and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Google Ads MCP Server FAQ

What is the Google Ads MCP server?

The Google Ads MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Google Ads data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Google Ads MCP server different from the official one?

The official Google Ads MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Google Ads MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Google Ads MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Google Ads, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Google Ads actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Google Ads MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Google Ads MCP locally, you'll see it.

What does the Google Ads MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Google Ads MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.