
Creator SEO MCP
io.github.Yoshyaes由 GitHub 账号 Yoshyaes 发布v0.1.1更新于 Oct 24, 2026
SEO MCP server for creators. Ranks Google Search Console opportunities by ad revenue, not clicks.
概览
面向内容创作者的 SEO 助手,读取 Google Search Console 数据,并按预估广告与联盟收入对关键词和页面机会排序。
- 可以做什么
- 它查询 Google Search Console,找出处于第 4-15 位的“临门一脚”关键词、单页表现、逐月流量衰减以及多页面争抢同一查询的问题。它还会抓取指定网址,对照目标查询检查标题、meta、标题层级和正文,并给出具体修改建议。六个工具可组合成完整的创作者 SEO 工作流,最终汇总为一份按收入加权的行动清单。
- 适用场景
- 适合运营内容站点或博客、希望按收益而非单纯点击量来决定先做哪些 SEO 优化的人。尤其适合依靠展示广告或联盟链接变现、已有 Search Console 数据并需要按页面优先级获得建议的创作者。
- 运行要求
- 以本地 Python 包方式运行(uvx 或 pip)。需要 Google Cloud OAuth 2.0 桌面客户端生成的 credentials.json 文件,其绝对路径通过 GOOGLE_CREDENTIALS_PATH 指定,并需启用 Search Console API 且拥有相应媒体资源的访问权限。可选环境变量 CREATOR_SEO_SITE_RPM 与 CREATOR_SEO_AFFILIATE_CATEGORIES 用于调整收入权重。仅限桌面端,访问 Google API 和抓取页面需要网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Creator SEO MCP,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
creator-seo-mcp
An MCP server for content creators that connects Google Search Console to your page content and ranks every SEO opportunity by estimated revenue, not vanity clicks.
Generic SEO tools surface raw GSC numbers. This one tells you which fix pays most, based on your actual display-ad RPM and affiliate commission rates.
What it does
Six tools, designed to work together in a full creator-SEO workflow:
Install
Or with pip:
Setup
1. Google Search Console credentials
Follow docs/gsc-setup.md to:
- Enable the Search Console API in Google Cloud
- Create an OAuth 2.0 Desktop client
- Download
credentials.json
2. Claude Desktop config
Add to your claude_desktop_config.json:
3. Claude Code config
4. Revenue config (optional but recommended)
Set your display-ad RPM so opportunities are ranked by real dollars:
See .env.example for all options.
Example agent prompts
- "Show me my top five revenue-weighted SEO opportunities for this week."
- "Which of my posts are losing traffic compared to last month?"
- "My Baldur's Gate 3 build guide is stuck on page 2. Audit it against its main keyword and tell me what to fix."
- "Find any posts that are competing with each other for the same search term."
- "What is the on-page gap between this article and the query it is trying to rank for?"
Two Average Gamers case study
Real output from get_top_opportunities, run live against Two Average Gamers (a top-200 gaming blog on Mediavine display ads and Amazon affiliate links) on 2026-08-25, over the trailing 28 days (392K impressions, 3.5K clicks per Search Console).
This is the actual "before" baseline, not a mockup. Dollar estimates use the default $15 RPM placeholder (set CREATOR_SEO_SITE_RPM to your real network RPM for accurate figures). Out of 147 scored opportunities across all three signal types, the top 5 by estimated revenue:
analyze_content_decay also flagged 40 pages losing clicks month-over-month on this run, the worst being a 100% drop (10 clicks to 0) on a Palworld lawsuit post and a 61% drop on a Palworld tower-boss guide, both worth a content refresh before the traffic they had is gone for good.
Update (2026-08-25): the title/H1 edits for the two striking-distance opportunities above are live. Re-running audit_page_onpage against the real pages confirms it:
No position or traffic movement to report yet, and that's expected, not a null result: Search Console's data has a 2-3 day freshness lag, so a same-day re-pull still covers the identical 2026-07-26 to 2026-08-22 window as the original baseline above, before any of these edits existed. Google also needs to re-crawl and re-rank the pages, which typically takes longer than the raw data lag. This section will be updated again once a GSC pull actually covers the post-edit period (realistically 2-3 weeks out) with the real position and click change, not before.
Contributing
Issues and PRs welcome. See CONTRIBUTING.md for guidelines.
License
MIT
来源:README.md,提交 c868317
工具
0版本历史
1- v0.1.1最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。