Enterprise Connectors
Google Ads logo. Google Ads MCP server connector.

Google Ads MCP Server

Google Ads MCP server — manage campaigns, keywords, and metrics.

Tools
0
Last Updated
Jan 1, 2024
Enterprise-grade security
SSO & authentication ready
Full governance & audit logs

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 0 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 Google Ads data

Retrieve structured information from this integration so your AI agents can read and reason over it.

Create Google Ads item

Create new records or resources inside this integration directly from your AI workflows.

Update Google Ads item

Safely update existing records with full auditability and guardrails enforced by Webrix.

Customize Tools

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

Edit descriptions
Change arguments
Select tools
Create New

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-ai-adramp-google-ads": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/ai-adramp-google-ads"
    }
  }
}

Cursor

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

Claude Code

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

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/ai-adramp-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.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.

Google Ads MCP Server | Willow