MCP.so
登录

Google Ads Intent MCP Server

@davidmosiah

基本信息

分类

其他

许可证

MIT

传输方式

stdio

作者

davidmosiah

提交者

David Batista

关于 Google Ads Intent MCP Server

Dry-run-first Google Ads search-term intent analyzer and negative-keyword MCP for agents.

Google Ads Intent MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "google-ads-intent": {
      "command": "npx",
      "args": [
        "-y",
        "google-ads-intent-mcp"
      ]
    }
  }
}

Google Ads Intent MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。

概览

What is Google Ads Intent MCP?

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.

How to use Google Ads Intent MCP?

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.

Key features of Google Ads Intent MCP

  • Dry-run analysis of exported search-term CSVs
  • Classifies intent into waste, buyer, research, or competitor
  • Drafts negative-keyword plans without applying them
  • Privacy audit and connection status introspection tools
  • Deterministic heuristic with optional LLM refinement
  • Buyer/conversion terms automatically protected from exclusion

Use cases of Google Ads Intent MCP

  • Reduce wasted ad spend by identifying non-converting search terms
  • Safely generate negative keyword plans before making live changes
  • Protect buyer-intent queries from accidental exclusion
  • Automate search-term analysis in agent-driven ad workflows
  • Local CSV analysis without exposing account credentials to agents

常见问题

1

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.

2

What are the runtime requirements?

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.

3

Where does the data live?

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.

4

What are the known limits?

The current version (v0.1) does not perform live mutations. It only analyzes CSV exports. Negative keyword plans are dry-run only.

5

What transport and authentication does it use?

The MCP server uses stdio transport. It does not require authentication for the server itself; account credentials are handled externally via environment variables.

评论

其他 分类下的更多 MCP 服务器