What does Google Ads Intent MCP do differently from alternatives?
It is dry-run-first: it never mutates Google Ads accounts directly. CSV analysis is local, and negative plans are drafted but not applied, making the safe path the default.
@davidmosiah
Basic information
Dry-run-first Google Ads search-term intent analyzer and negative-keyword MCP for agents.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"google-ads-intent": {
"command": "npx",
"args": [
"-y",
"google-ads-intent-mcp"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Google Ads Intent MCP is a dry-run-first search-term intent analyzer for agents that classifies Google Ads search terms and drafts negative-keyword plans without making live account changes. It is built for MCP clients like Codex, Claude, Cursor, Hermes, and OpenClaw, helping reduce wasted spend while protecting buyer-intent queries.
Install via pipx: pipx install google-ads-intent-mcp (or pipx install "google-ads-intent-mcp[mcp]" for MCP support). Then run the MCP server with google-ads-intent-mcp. Recommended first calls: google_ads_connection_status, google_ads_privacy_audit, google_ads_analyze_search_terms, and google_ads_build_negative_plan. The CLI offers commands like google-ads-intent manifest, doctor, privacy-audit, classify, analyze-csv, and plan-negatives.
It is dry-run-first: it never mutates Google Ads accounts directly. CSV analysis is local, and negative plans are drafted but not applied, making the safe path the default.
Python 3.12+ with pipx. No API keys are required for the default heuristic classifier. An optional LLM refinement path requires `OPENAI_API_KEY` and the `openai` package.
All CSV analysis is performed locally. Search terms, costs, and clicks are processed on the user’s machine. OAuth tokens and developer tokens should remain in the local environment.
The current version (v0.1) does not perform live mutations. It only analyzes CSV exports. Negative keyword plans are dry-run only.
The MCP server uses stdio transport. It does not require authentication for the server itself; account credentials are handled externally via environment variables.

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
A search tool helps dev to solve the naming things problem.
Open-source MCP to use Blender with any LLM

Request dedicated senior developers to work on your project, write job descriptions, and prep technical interviews — all without leaving your Claude chat. Just describe what you need, and Lemon.io MCP does the rest. 1–3
Comments