← Back to directory
G

Google Ads MCP Server

Official
Official MCP server for interacting with the Google Ads API
GitHub source repository ↗
★ 893 Stars Category · Other Very popular Source revision 88f0467b9e53
56FMRS · C
Reliability
10/20
Security and permissions
10/20
Maintenance
12/20
Documentation
12/20
Setup experience
12/20

This is an official MCP server maintained by Google for interacting with the Google Ads API. It provides query tools and metadata resources, supports multiple authentication methods, and can be deployed locally or in the cloud. Suitable for users looking to integrate AI assistants into advertising account management, but note data exposure permissions and token management.

Read the FMRS scoring method →

The Google Ads MCP Server is an official server that provides tools and resources for AI agents and LLMs to query and interact with Google Ads data. It supports searching advertising account information, retrieving resource metadata, listing accessible customers, and offers resources such as discovery document, metrics, segments, and release notes. The server supports multiple authentication methods including FastMCP OAuth proxy, Application Default Credentials, or the Google Ads API Python client library, and can run via local stdio or remote streamable-http transport.

Tools

search
Retrieves information about the Google Ads account.
get_resource_metadata
Retrieves metadata about a Google Ads API resource type, for example 'campaign', to understand the data structure and available fields.
list_accessible_customers
Returns IDs of customers directly accessible by the user authenticating the call.

Setup

  1. Install pipx.
  2. Obtain a developer token following official instructions, with at least Explorer access.
  3. Enable the Google Ads API in your Google Cloud project.
  4. Configure credentials: choose FastMCP OAuth proxy, Application Default Credentials, or the Google Ads Python client library.
  5. Add the server to your MCP client configuration, setting environment variables like GOOGLE_ADS_DEVELOPER_TOKEN and credential path.
  6. If using OAuth proxy, set the relevant environment variables and run the server as a separate process.
claude_desktop_config.json
{
  "mcpServers": {
    "google-ads-mcp": {
      "command": "pipx",
      "args": [
        "run",
        "--spec",
        "git+https://github.com/googleads/google-ads-mcp.git",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "PATH_TO_CREDENTIALS_JSON",
        "GOOGLE_PROJECT_ID": "YOUR_PROJECT_ID",
        "GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_DEVELOPER_TOKEN"
      }
    }
  }
}

Fit and risk

Best for

  • Marketers
  • Data analysts
  • Developers using AI assistants to manage Google Ads accounts
  • Teams needing automated advertising reporting and analysis

Not for

  • Users without a Google Ads account or a valid developer token
  • Users with test-only tokens unable to access production accounts
  • Users requiring modifications to ad budgets or bids (server only provides query and metadata capabilities)
  • Fully offline environments (requires access to Google Ads API)

Required permissions

  • Requires Google Ads API access token, typically via OAuth 2.0
  • Requires a developer token with at least Explorer access
  • Requires Google Ads API enabled in your Google Cloud project
  • Credentials must include the adwords scope

Risks and side effects

  • The server exposes your advertising data to the connected AI agent or LLM
  • API calls may contain sensitive business data
  • If credentials are leaked, unauthorized access could occur
  • Quota and rate limits may cause service interruptions if exceeded

Troubleshooting

  1. Check that the developer token has production access; otherwise an error occurs
  2. Verify the Google Ads API is enabled in your Google Cloud project
  3. Validate the credential file path and adwords scope
  4. For OAuth proxy, ensure all related environment variables are set correctly and check server logs
  5. Confirm environment variable names and values in MCP client configuration

Use cases

Query the number of active campaigns in the advertising account
Retrieve campaign performance data
List all customer accounts the user has access to
Explore the Google Ads API resource structure and available fields

Supported clients

Antigravity CLIFull support
Antigravity Code AssistFull support
Claude CodeFull support
CursorFull support
VS Code with CopilotFull support