mcpField
G
Google Ads Intent Mcp

Google Ads Intent Mcp

Local
github.comBusiness & Marketing2Updated 4w ago

About Google Ads Intent Mcp

Google Ads Intent Mcp analyzes Google Ads search terms and drafts negative-keyword plans for agents. It suits teams reviewing exported data before reducing wasted spend; its default heuristic analysis is local, and v0.1 does not modify live accounts.

Key features

  1. 01Classify terms into four intent groups
  2. 02Analyze CSV exports locally
  3. 03Draft dry-run negative-keyword plans
  4. 04Protect buyer and conversion terms
  5. 05Provide connection status and privacy audits

Use cases

  1. 01Screen exported terms for wasted traffic
  2. 02Identify buyer, research, and competitor intent
  3. 03Prepare negative plans for human review
  4. 04Check analysis boundaries before processing ad data

MCP support

It exposes stdio MCP tools for term classification, CSV analysis, negative-keyword planning, connection status, and privacy audits. Negative plans are dry-run only and are not applied to live accounts.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"google-ads-intent": {
"command": "uvx",
"args": [
"google-ads-intent-mcp"
],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
"GOOGLE_ADS_CLIENT_ID": "<GOOGLE_ADS_CLIENT_ID>",
"GOOGLE_ADS_CLIENT_SECRET": "<GOOGLE_ADS_CLIENT_SECRET>",
"GOOGLE_ADS_REFRESH_TOKEN": "<GOOGLE_ADS_REFRESH_TOKEN>",
"GOOGLE_ADS_CUSTOMER_ID": "<GOOGLE_ADS_CUSTOMER_ID>"
}
}
}
}
Run commanduvx google-ads-intent-mcp
Environment variables to set
GOOGLE_ADS_DEVELOPER_TOKENSecretGoogle Ads developer token used only when live Google Ads access is configured.
GOOGLE_ADS_CLIENT_IDOAuth client ID used only when live Google Ads access is configured.
GOOGLE_ADS_CLIENT_SECRETSecretOAuth client secret used only when live Google Ads access is configured.
GOOGLE_ADS_REFRESH_TOKENSecretOAuth refresh token used only when live Google Ads access is configured.
GOOGLE_ADS_CUSTOMER_IDGoogle Ads customer ID for live account queries.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypigoogle-ads-intent-mcp0.1.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Google Ads Intent MCP

Google Ads Intent MCP
Dry-run-first Google Ads search-term intent analyzer + negative-keyword MCP for agents.
Look at search terms safely before spending budget.

npm version npm downloads License MIT Built for MCP

GitHub stars CI status Part of the Delx agent stack Category

mcp-name: io.github.davidmosiah/google-ads-intent-mcp

⭐ If this agent-first tool helps your workflow, please star the repo. Stars make this tooling easier for other builders to discover and help Delx keep shipping open infrastructure.
🧱 Part of the Delx agent stack — 15 open-source MCP servers across body, reach and coordination.


Dry-run-first Google Ads search-term intent analyzer for agents. It helps Codex, Claude, Cursor, Hermes, OpenClaw and other MCP clients classify search terms, protect buyer intent and draft negative-keyword plans from CSV exports before any live account change.

Use it when an agent needs to reduce wasted spend without accidentally excluding buyer-intent queries.

HTTP (v2 stateless)

Not shipped. Optional FastMCP extra is stdio-only (same skip as delx-agent-utilities: no /health without extra Starlette routes). Dry-run analysis stays request-stateless over stdio.

Why It Exists

Google Ads cleanup is risky when agents act directly on accounts. This package makes the safe path the default:

  • analyze exported search-term CSVs locally
  • classify waste, buyer, research and competitor intent
  • draft negative-keyword plans without applying them
  • expose manifest, connection_status and privacy_audit before action tools
  • keep live mutation out of v0.1

Install

pipx install google-ads-intent-mcp

With MCP support:

pipx install "google-ads-intent-mcp[mcp]"

Published on PyPI: google-ads-intent-mcp. Release automation uses PyPI Trusted Publishing, so GitHub Actions can publish future versions without long-lived PyPI tokens. See docs/pypi-publishing.md.

CLI

google-ads-intent manifest --client codex
google-ads-intent doctor
google-ads-intent privacy-audit
google-ads-intent classify "free robux generator no verification"
google-ads-intent analyze-csv --csv examples/search_terms.csv
google-ads-intent plan-negatives --csv examples/search_terms.csv
Intent classification

The classifier is a deterministic, dependency-free heuristic with broad, cross-vertical signal coverage (ecommerce, B2B/SaaS, local services, health, finance, education and more) — not just gaming traffic. It sorts each search term into waste, buyer, research or competitor intent and protects converting queries from being flagged as negatives.

An optional LLM/embeddings-backed refinement path is available and is off by default. It requires no extra dependencies or API keys for normal use, and always falls back to the heuristic when no backend is configured:

# Opt in via flag (falls back to the heuristic if nothing is configured)
google-ads-intent --llm classify "crm software pricing"

# Or via environment variable
GOOGLE_ADS_INTENT_LLM=1 google-ads-intent analyze-csv --csv export.csv

To actually call a backend, set OPENAI_API_KEY (and optionally GOOGLE_ADS_INTENT_LLM_MODEL, default gpt-4o-mini) and install the openai package. Without those, --llm is a no-op that keeps the heuristic result. Each classification reports which path produced it via a source (heuristic or llm) field.

MCP

google-ads-intent-mcp

Hermes-style config:

mcp_servers:
  google_ads_intent:
    command: google-ads-intent-mcp
    args: []
    sampling:
      enabled: false

Recommended first calls:

  1. google_ads_connection_status
  2. google_ads_privacy_audit
  3. google_ads_analyze_search_terms
  4. google_ads_build_negative_plan

Agent Surfaces

ToolPurpose
google_ads_agent_manifestInstall/runtime guidance for agent clients
google_ads_connection_statusCSV/API readiness without credentials
google_ads_privacy_auditDry-run, account and export boundaries
google_ads_classify_search_termSingle-query intent classification
google_ads_analyze_search_termsBatch CSV-style analysis
google_ads_build_negative_planDry-run negative keyword plan

Copy-Paste Agent Prompt

Use google-ads-intent-mcp. First call google_ads_connection_status and google_ads_privacy_audit.
Analyze the search terms, protect buyer/conversion queries, and return a dry-run negative plan only.

CSV Format

The parser accepts common exported columns such as:

  • search_term, Search term, Query
  • cost, Cost, cost_micros
  • clicks, Clicks
  • conversions, Conversions, Conv.
  • impressions, Impr., Impressions

Safety Model

  • CSV analysis is local.
  • Negative plans are dry-run only.
  • Buyer/conversion terms are protected from automatic exclusion.
  • OAuth tokens, developer tokens and account identifiers should stay in local environment/config files.

Development

python3 -m venv .venv
. .venv/bin/activate
pip install -e ".[dev]"
pytest
python -m compileall -q src

📧 Contact & Support

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.