
Google Ads Intent Mcp
io.github.davidmosiah由 GitHub 账号 davidmosiah 发布v0.1.1更新于 Oct 24, 2026
Dry-run-first Google Ads search-term intent analyzer and negative-keyword MCP for agents.
概览
一个本地 MCP 服务器,从 CSV 导出中分类 Google Ads 搜索词意图,并生成仅演练的否定关键词方案,保护购买意图查询。
- 可以做什么
- 对单个搜索词或批量导出的搜索词进行分类,归入浪费、购买、研究或竞品意图;可选的 LLM 精炼路径默认关闭,未配置后端时回退到启发式分类器。在本地分析导出的搜索词 CSV,接受搜索词、费用、点击、转化和展示等常见列名。生成否定关键词方案但不实际应用,并保护购买和转化词不被排除。在使用操作类工具前,报告安装与运行指引、无需凭据的 CSV/API 就绪状态,以及演练、账户和导出边界。
- 适用场景
- 当助手需要检查 Google Ads 搜索词导出以找出浪费支出并建议否定关键词,同时避免误排除有转化的查询时使用。适合以演练为先、不希望改动线上账户的清理流程。
- 运行要求
- 需要本地 Python 运行环境;安装 PyPI 包 google-ads-intent-mcp,使用 MCP 时需加 mcp 附加项。CSV 分析无需凭据。实时 Google Ads 访问为可选项,使用 GOOGLE_ADS_CLIENT_ID、GOOGLE_ADS_CLIENT_SECRET、GOOGLE_ADS_DEVELOPER_TOKEN、GOOGLE_ADS_REFRESH_TOKEN 和 GOOGLE_ADS_CUSTOMER_ID。可选的 LLM 精炼需要 OPENAI_API_KEY 和 openai 包。
安装
在 SourceWeft 中
- 打开 控制台中的 Google Ads Intent Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
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_statusandprivacy_auditbefore action tools - keep live mutation out of v0.1
Install
With MCP support:
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
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:
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
Hermes-style config:
Recommended first calls:
google_ads_connection_statusgoogle_ads_privacy_auditgoogle_ads_analyze_search_termsgoogle_ads_build_negative_plan
Agent Surfaces
Copy-Paste Agent Prompt
CSV Format
The parser accepts common exported columns such as:
search_term,Search term,Querycost,Cost,cost_microsclicks,Clicksconversions,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
📧 Contact & Support
- 📨 [email protected] — general questions, integration help, partnerships
- 🐛 Bug reports / feature requests — GitHub Issues
- 🐦 Updates — @delx369 on X
- 🌐 Site — wellness.delx.ai
来源:README.md,提交 30098d3
工具
0版本历史
1- v0.1.1最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分