
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 分
請在儲存庫或註冊中心條目中宣告授權條款。