
Seo Monster
io.github.avansaber由 GitHub 账号 avansaber 发布v0.9.3更新于 Oct 25, 2026
Local-first SEO MCP: track AI citations, Search Console, GA4, PageSpeed, Cloudflare, IndexNow, CrUX.
概览
本地运行的 SEO 工具集,让助手获取 Search Console、GA4、PageSpeed、Cloudflare 和 IndexNow 数据,并执行 SEO 审计与内容工作流。
- 可以做什么
- 查询 Search Console 的点击、展示、热门查询与页面、周期对比、URL 检查、站点地图及查询机会与缺口,并支持多站点组合汇总和覆盖率审计。读取 GA4 自然搜索报告,并基于自有数据排序内容选题机会。运行 PageSpeed Insights 与 CrUX 检测,审计 Cloudflare 区域、DNS、分析和设置,并提交 IndexNow。检查页面的技术 SEO:meta、规范链接、重定向链、混合内容、robots.txt、站点地图和结构化数据。通过十三个命名工作流提示串联工具,例如每周复盘、上线前检查、迁移检查和从内容简报生成文章。查看哪些服务已配置并可用。
- 适用场景
- 适合 SEO 从业者、代理机构和站点所有者,让助手分析搜索表现、审计技术与结构化数据问题、跟踪 AI 答案引擎引用,或基于自有 Search Console 数据撰写并校验内容。
- 运行要求
- 以本地 Python 包运行(需 Python 3.11+ 及 uv/uvx,或使用 Claude Desktop 捆绑包)。Search Console、Indexing 和 GA4 工具需要 Google OAuth 桌面应用客户端密钥 JSON 并完成一次浏览器授权,或使用服务账号。可选密钥:PSI_API_KEY、CF_API_TOKEN、SEO_MCP_INDEXNOW_KEY、DataForSEO、Open PageRank、Google Ads 及 AI 服务商密钥。需要网络访问。
安装
在 SourceWeft 中
- 打开 控制台中的 Seo Monster,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Don't learn another SEO dashboard. Just ask.
The open-source SEO analyst that lives inside the AI assistant you already use —
working from your own Search Console, Analytics, and PageSpeed data, on your machine.
[PyPI version] [Python versions] [Downloads] [Tests] [License: MIT] [GitHub stars]
You don't open a new tool — you just ask, in plain English, inside Claude (or Cursor / Cline / Codex):
You "What should I write about next?"
🦖 SEOMonster Pulls your Search Console and surfaces three topics you're almost ranking for — positions 8–20 with real demand — ranked by opportunity. Say the word and it drafts the brief.
70 tools across Search Console, GA4, PageSpeed, Cloudflare, AI-citation tracking, keyword discovery, and technical SEO — every one returning the same JSON result envelope, every one driven by your own credentials. No new dashboard to learn; you chat with the assistant you already use.
[!NOTE] Published on PyPI as
seo-monster(so the command isuvx seo-monster). The import package isseo_mcp;seo-mcpis a dev/local alias. The package ships zero secrets — every credential is resolved at runtime from your own environment or config file.
- Your data, your machine. User-credential-driven; nothing is sent to any third party.
- Read-first, safe by default. Reads always work; the two routine writes (sitemap submit, indexing request) are on by default; the Cloudflare write tools (cache purge, redirects, settings, managed robots.txt) are gated behind
SEO_MCP_ALLOW_DESTRUCTIVE, and the riskier ones also need a per-callconfirmtoken. - Lean. Standard library + the
mcpSDK + the Google client libraries; PageSpeed and Cloudflare ride onurllib, no extra HTTP dependency.
Quickstart
[!TIP] Fastest path: the one-click install buttons above. Or add it to any MCP client by hand:
Run the one-time Google sign-in once — uvx --from seo-monster seo-monster auth — then ask your assistant to call system_status to confirm what's connected. Full per-client setup and credentials are in Install and Auth.
How it works
SEOMonster is a stdio MCP server: your AI host launches it, it calls Google / Cloudflare / the AI engines with your credentials, and returns a consistent JSON envelope the assistant reads back to you in plain language.
Requirements
For the .mcpb bundle path (Claude Desktop): just Claude Desktop on macOS
or Windows. The bundle declares Python 3.11+ as a runtime; Claude Desktop
materializes the environment for you. No prior uv install needed.
For the uvx path (Cursor, Cline, Codex, advanced Claude Desktop): Python
3.11 or newer plus uv (which provides uvx).
Find the absolute path to uvx with which uvx; GUI hosts do not read your
shell profile, so MCP configs need the full path.
Tools
70 tools, grouped by service. All return the same result envelope (see
Result envelope). Call system_status first if unsure what
is configured. The server also publishes thirteen named workflow prompts.
Cross-service
system_status- which services are configured/reachable, the Google auth method and scopes, whether destructive mode is on, the full tool catalog, and the list of registered prompts.
📂 Browse all 70 tools — grouped by service (GSC · GA4 · AI/GEO · keyword discovery · content · PageSpeed/CrUX · Cloudflare · IndexNow · technical · schema). Click to expand.
Google Search Console (18)
Workhorses
gsc_list_properties- properties the credentials can see, with permission level and a derivedwritableflag (true forsiteOwner/siteFullUser).gsc_search_analytics- the workhorse: clicks/impressions/CTR/position by dimensions, date range, filters, anddata_state.gsc_top_queries/gsc_top_pages- convenience top-N wrappers.gsc_compare_periods- current vs prior window with per-key deltas. v0.2.0 addedsort_by,sort_dir,min_delta_clicks/_impressions/_position,anomalies_only+sigma_threshold, andtopfor one-call movers / losers / outliers reporting.gsc_inspect_url- URL Inspection (index verdict, coverage, canonicals).gsc_batch_inspect_urls- inspect up to 25 URLs, per-URL failures collected.gsc_list_sitemaps- registered sitemaps and their status.gsc_submit_sitemap- submit a sitemap (write, un-gated; needs the writable scope). Accepts eithersitemap_url(friendly) orfeedpath(raw API field).gsc_request_indexing- request (re)crawl via the Indexing API (write, un-gated). Accepts singularurlorurls.
Query intelligence (v0.2.0)
gsc_query_opportunities- queries already ranking top N with below-target CTR. Title and meta optimization candidates.gsc_query_gaps- queries that draw impressions but barely any clicks. Content opportunity signal.gsc_new_queries- queries appearing in the current window with no prior impressions. Emerging topics.gsc_top_pages_by_query- which pages rank for a specific query. The cannibalization audit input.
Multi-property + lifecycle (v0.5.0)
gsc_portfolio_summary(days, include?, exclude?)- multi-property fleet view. Per-property one-row summary (clicks, impressions, CTR, position) for the last N days, plus a portfolio-level rollup. Honors optionalinclude/excludefilters. The single fastest answer to "how is the whole portfolio doing?" across agency or multi-brand setups.gsc_trending_pages(days, limit)- pages whose impressions grew most over the last N days vs the prior N days. Wrapper ongsc_compare_periodswithdimensions=["page"], sort_by="delta_impressions", sort_dir="desc".gsc_decaying_pages(days, limit)- same wrapper, ascending sort. Pages to rescue.gsc_coverage_audit(urls, site_url?)- heuristic coverage audit. The GSC Index Coverage report is not exposed in the API; this tool takes a user- supplied URL list (typically pulled from a sitemap) and bulk-inspects each, then rolls up verdicts (PASS / PARTIAL / FAIL) and coverage_state frequencies.
Content intelligence (4)
content_opportunities(site_url?, days?, count?, impressions_min?)- ranks data-grounded content topics from your own Search Console data: fuses CTR-vs-expected gap (curve self-calibrated from your own per-position CTR), striking-distance position, demand, and momentum into a transparent opportunity score; flags cannibalization. If a GA4 property is configured, it also weights each topic by the organic conversions its top page already drives (up to +50%), so topics that convert rank higher;filters_applied.ga4_value_statusreports whether that ran and why (applied/no_ga4_property/ga4_unreachable/no_conversions). Prioritizes demand you already have; does not do cold-start keyword research or write the content. Pairs with the content workflow prompts below. (GA4 weighting v0.7.3) v0.9.0 adds an additive per-candidatewinnabilityblock (banded: striking-distance + topical- proximity, GSC-personalization tier; existing fields unchanged).content_brief_data(target_query, competitor_urls?, topic?, site_url?, days?)- data-wired backing for a content brief: fetches the competitor pages (or your own GSC-ranking pages as a fallback) and returns the heading union, median word-count floor, schema types, and entity coverage, plus the 2026 GEO writing directives and validation rules. The host writes the prose; SEOMonster brings rules + evidence. Backs thecontent_briefprompt. (v0.9.0)topic_cluster_map(cluster_path | pillar_url, site_url?, days?, impressions_min?)- maps a content cluster from your own GSC data and surfaces missing subtopics. Classifies each cluster query into defend / optimize / create / monitor by demand and best position; the create quadrant is your missing-subtopic list. Flags cannibalization. GSC-only; honest about the ~47% query anonymization. (v0.9.0)
rank_change_attribution(url | urls, change_date, query?, site_url?, pre_days?, post_days?, gap_days?, control_scope?)- estimates whether an on-site change moved a page's clicks via difference-in-differences against a matched control group (never a naked before/after). Returns an estimated lift with a 95% CI, a three-state verdict (likely_positive / likely_negative / inconclusive), and a confounders block that auto-detects the 2025 GSC data-regime breaks (impression bug, num=100) and downgrades position reliability. Observational, not causal -- a server-side split test is the only true causal test. GSC-only. (v0.9.0)
AI / GEO citation (3, v0.9.0) - whether the AI answer surfaces reach and cite you.
ai_citation_readiness(url)- is a page structured to be extracted/cited by LLM answer engines? Leads with a render-blindness check (GPTBot / ClaudeBot / PerplexityBot fetch but do not run JS, so a client-rendered SPA is invisible to them), then scores evidence-backed signals (statistics, quotations, cited sources, no keyword-stuffing). schema.org / FAQ / llms.txt are reported as informational only -- the 2026 evidence does not support them as AI-citation drivers, so they are not scored. Free, HTTP-only.ai_referral_overview(property_id?, site_url?, days?)- first-party AI traffic: GA4 referral sessions from AI apps (the nativeai-assistantchannel plus a configurable source-host regex) and AI-crawler robots coverage (GPTBot, ClaudeBot, PerplexityBot, ...). Surfaces the ~70% dark-traffic undercount and keeps AI-Overview clicks (counted as Organic) separate. Free.ai_citation_track(prompts, brand, brand_domains?, competitors?, engines?, samples?)- sampled brand mention + citation share-of-voice across AI engines (Perplexity / OpenAI / Anthropic / Gemini APIs + Google AI Overviews via DataForSEO) for a managed prompt set, vs competitors. N samples/prompt (default
- with a 95% CI, share-of-voice, and run-to-run volatility -- NOT an "AI rank" (single runs are statistically meaningless). Discloses that developer-API output differs from the logged-in consumer UI and that AIO has no API. Paid + non-deterministic. Needs at least one engine key and/or DataForSEO.
Keyword discovery (3, v0.9.0) - find terms you don't already rank for.
gsc_keyword_expand(candidates, site_url?, days?, impressions_min?)- you (the host) brainstorm candidate terms from your winning queries; this grounds each against your own Search Console data (footprint covered / thin / none) with a sibling-strength confidence band. "none" = no VISIBLE footprint (GSC hides ~75% of impressions), so net-new terms are scored hypotheses. Free.serp_adjacency_expand(seeds, include_paa?)- expand seed terms into adjacent terms. FREE core: Google Autocomplete (no key). Optional People-Also-Ask + related searches via DataForSEO. Returns per-seed suggestions plus the aggregated net-new terms; degrades gracefully without a key.keyword_universe(target_domain?, competitors?, keywords?, limit?)- optional, paid. Core value: the competitor keyword GAP (DataForSEO Domain Intersection; no Google equivalent). Optional search volume / difficulty / intent via a provider chain (DataForSEO, else Google Ads volume-only). External volume is a degraded directional signal -- a tiebreaker, never a gate.
Google Analytics 4 (7)
ga4_run_report- the workhorse: arbitrary dimensions/metrics/date range, optional dimension filter and ordering.ga4_top_landing_pages- top landing pages, organic-only by default.ga4_traffic_by_channel- sessions/engagement/conversions by channel group.ga4_organic_search_overview- organic totals plus a day-by-day trend.ga4_setup_audit(property_id?)- read-only SEO-measurement-readiness audit: web data stream, key events, data retention, content-group dimensions, and (v0.7.4) enhanced measurement, internal site search, and Google Signals. Severity-graded with a benign exception per finding. Uses the GA4 Admin API over REST (analytics.readonly; no extra dependency). (v0.7.0)ga4_site_search(days?, limit?)- internal site-search query report (a direct content-gap signal); honest envelope when no real search terms. (v0.7.1)ga4_landing_page_conversions(days?, organic_only?, limit?)- organic landing pages ranked by conversions. (v0.7.1)
PageSpeed Insights (2)
psi_analyze- Lighthouse scores, lab Core Web Vitals, and field (CrUX) Core Web Vitals for a URL. Defaults to the mobile strategy. Field data carries afield_data_note: Google is deprecating PSI field data, so usecrux_snapshot/crux_historyfor durable field metrics.psi_opportunities(url, strategy?)- the actionable Lighthouse "opportunity" audits (with estimated savings) plus the SEO-category audits, severity-graded. Lab data only. An on-page-basics checklist, not a ranking predictor. (v0.7.1)
Cloudflare (13)
cf_list_zones- zones the token can see.cf_zone_info- status, plan, name servers for a zone.cf_list_dns- DNS records (read-only); useful for verifying canonical host and TXT verification records during migrations.cf_web_analytics- read-only edge Web Analytics (RUM), to compare against GA4. Cloudflare returnshost: nullfor some sites; pass thesite_tagto look those up explicitly.cf_purge_cache- purge specific URLs (gated).cf_purge_cache_all- purge an entire zone (gated + confirm token).cf_settings_audit(zone?)- read-only audit of SEO-relevant Cloudflare zone settings (SSL mode, Always-Use-HTTPS, HSTS, Automatic HTTPS Rewrites, Brotli, cache TTL). Severity-graded with a "verify, not fail" discipline because CF cannot see the origin; HSTS is never a hard failure. Needs Zone Settings Read on the token. Each finding carries a machine-readablefixhint (the exactcf_settings_updatesetting + recommended value) to chain audit -> fix. (v0.7.1)cf_settings_update(settings, zone?, confirm?, acknowledge_hsts_risk?, dry_run?)- write the SEO/crawl/security settings the audit grades (SSL mode, Always-Use-
HTTPS, Automatic HTTPS Rewrites, Brotli, browser cache TTL, HSTS), closing the
audit -> remediate loop. Gated. ssl_mode or any HSTS-raise needs
confirm=<zone>(HSTS-raise also needsacknowledge_hsts_risk=true); validates locally, supportsdry_run, and re-runs the audit so you see the finding clear. Needs Zone Settings:Edit (vs the audit's Read). (v0.7.10)
- write the SEO/crawl/security settings the audit grades (SSL mode, Always-Use-
HTTPS, Automatic HTTPS Rewrites, Brotli, browser cache TTL, HSTS), closing the
audit -> remediate loop. Gated. ssl_mode or any HSTS-raise needs
cf_list_redirects(zone?)- list a zone's single (dynamic) redirect rules plus the account's Bulk Redirect lists (read-only). Call before any redirect write so nothing is clobbered. (v0.7.8; bulk lists added v0.7.9)cf_create_redirect(source, target, status_code?, ...)- create one edge redirect (e.g. a 301 for a renamed URL). Gated. Pre-flights the target (no redirecting to a dead URL), refuses loops/duplicates, supportsdry_run. (v0.7.8)cf_delete_redirect(rule_id, zone?)- remove a single-redirect rule by id (rollback for cf_create_redirect). Gated. (v0.7.8)cf_bulk_redirect_upsert(items, list_name, confirm, ...)- create/append many redirects at once via an account-level Bulk Redirect List (for migrations). Gated + a confirm token equal tolist_name. Validates every item locally first and rejects the whole batch on any bad item (never half-applies); supportsdry_run. (v0.7.9)cf_managed_robots(action, zone?, ...)- get / configure / disable Cloudflare's managed robots.txt and Content-Signals policy (these ride on the zone's Bot Management config).action="get"reads the current state (read-only, un-gated).action="configure"sets the managed robots.txt (managed_robots), the Content-Signals variant (cf_robots_variant: off / policy_only), and the AI-bot blocking levers (ai_bots_protection,content_bots_protection,crawler_protection).action="disable"turns the managed robots.txt and the policy back off. Managed robots.txt and the Content-Signals policy are mutually exclusive in Cloudflare, so the valid combinations aremanaged_robots=true+cf_robots_variant="off"(managed robots.txt) ORmanaged_robots=false+cf_robots_variant="policy_only"(the policy); the tool rejects the invalid combo locally withINVALID_INPUT. A custom Content-Signal line (e.g. fromrobots_ai_posture) is not a managed option - put that in your origin robots.txt. Writes are gated, needconfirm=<zone>, and supportdry_run; reads are safe (GET -> overlay -> PUT, so nothing else in the config is clobbered). Every response carries a caveat separating the stated-preference signals (Content-Signals, honored only by adopting crawlers and ignored by Googlebot) from the levers that actually enforce at the edge. Needs Bot Management:Edit for writes (Read for get). (v0.8.2)
IndexNow (2, v0.2.0)
indexnow_submit(url)- submit a single URL to Bing, Yandex, Naver, Seznam, Yep. Complements (does not replace)gsc_request_indexing, which only talks to Google. RequiresSEO_MCP_INDEXNOW_KEYplus a verification file athttps://<your-host>/<key>.txt(see IndexNow setup for the full key + file format + same-host rules).indexnow_bulk_submit(urls)- up to 10,000 URLs sharing one host in a single POST. Mixed-host batches are rejected client-side withINVALID_INPUTbefore any network call. TheSEO_MCP_INDEXNOW_KEY_LOCATIONenv var overrides the default verification-file URL when your CDN rewrites/key.txtpaths.
Technical SEO (8, v0.3.0) - no credentials needed; built-in HTTP client.
inspect_meta(url)- on-page surface in one call: title, meta description, meta robots, canonical, Open Graph + Twitter Card tags, hreflang, H1 count.check_canonical(url)- canonical-link audit: self-referential / cross-host / protocol-mismatched / trailing-slash drift / canonical target reachable.mixed_content_check(url)- parses an HTTPS page and flags anyhttp://references (img / script / iframe / form action / srcset). No-op forhttp://.redirect_chain_audit(url, max_redirects=10)- walks the chain hop by hop. Flags long chains, protocol downgrades, loops, non-2xx terminus.robots_txt_validate(site_url, probes?)- parses robots.txt (per-group rules + sitemaps + Content-Signals), optionally verdicts (user_agent, url) probes using RFC 9309 longest-match (matches what Google + Bing actually do, not stdlib's first-match). Also detects a stale edge-cached robots.txt (cache-bust comparison; re-parses from the fresh content) and a Cloudflare Managed robots.txt / Content-Signals policy overriding your origin - catching false-clean robots on migrated/CF-fronted sites. (v0.8.0)sitemap_validate(sitemap_url)- validates a sitemap or sitemap-index XML, counts entries, flags oversize + cross-host + missing lastmod..gztransparent.sitemap_health(sitemap_url, sample_size=25)- sample-HEAD audit. Status histogram + first non-2xx examples.robots_ai_posture(goal?, sitemap_url?)- deterministic, offline advisor for the Content-Signals levers (search/ai-input/ai-train). Takes a business goal (content_authoritydefault /maximize_visibility/protect_ip), recommends a posture with a plain-language rationale, lays out the trade-off alternatives, and emits a ready-to-apply artifact: theContent-Signal:directive line plus a full suggested robots.txt. No network, no writes. Every response carries the mandatory caveat that Content-Signal is honored only by adopting crawlers, is ignored by Googlebot, and is not a ranking factor. (v0.8.1)
Chrome UX Report (2)
crux_history(url? | origin?, form_factor?, metrics?)- 25 weeks of p75 Core Web Vitals via the CrUX History API. ReusesPSI_API_KEY; works anonymously at a tighter rate limit when no key is configured.crux_snapshot(url? | origin?, form_factor?)- the current p75 Core Web Vitals (point-in-time, vs the history). Each metric reports a category (GOOD / NEEDS_IMPROVEMENT / POOR); the rolled-up rating isoverall_category. Time metrics usep75_ms; the unitless CLS usesp75. Small origins return ano_dataenvelope. (v0.7.1)
Structured data + cross-site + on-page (7) - no new credentials (the v0.9 SERP auto-fetch is optional).
inspect_schema(url)- extract every JSON-LD block from a page; report the schema.org @type counts and a sample entity per type.validate_schema(url, types?)- verdict each JSON-LD entity against the Google Rich Results required-field set. Covers Article, NewsArticle, BlogPosting, Product, FAQPage, BreadcrumbList, Organization, LocalBusiness, Event, Review, Recipe. Per-entity verdict plus missing_required and missing_recommended lists.hreflang_consistency_check(urls)- cross-page hreflang audit on a user-supplied URL set. Flags missing reciprocity, broken hreflang targets, duplicate hreflang on one page, missing self-link, missing x-default when there are 3+ language variants.internal_link_graph(start_url, max_depth=2, max_pages=50)- small BFS crawl within the same host. Per-page in-degree + out-degree, orphan pages, broken internal links, depth distribution. Hard caps (max_depth <= 4, max_pages <= 200) so a misuse never melts the host.lighthouse_budget(url, budget)- wrapspsi_analyzeand verdicts the results against a budget dict, e.g.{performance: 80, LCP_ms: 2500, CLS: 0.1}. Per-metric pass/fail and an overall verdict. Useful as a CI / pre-deploy gate inside an LLM session. ReusesPSI_API_KEY.internal_link_recommend(start_url, site_url?, days?, position_min?, position_max?, relevance_floor?, limit?)- recommends specific source->target internal links from high-in-degree pages
to GSC striking-distance pages (default position 8-20 with real impressions),
with anchor text. Ranks sources by lexical relevance + internal authority, skips
pages that already link the target, balances anchor text, and never suggests
nofollow. Built on
internal_link_graph+ GSC. Free. (v0.9.0)
- recommends specific source->target internal links from high-in-degree pages
to GSC striking-distance pages (default position 8-20 with real impressions),
with anchor text. Ranks sources by lexical relevance + internal authority, skips
pages that already link the target, balances anchor text, and never suggests
nofollow. Built on
onpage_serp_gap(target_url, query?, competitor_urls?, max_competitors?)- the headings, entities, and schema the top SERP results have that a target page lacks, turned into on-page actions. FREE with caller-suppliedcompetitor_urls; optional DataForSEO SERP auto-fetch byquery, which also returns winnability signals (serp_compositionAI-Overview / UGC zero-click risk) and, with Open PageRank, competitor domain authority. Surfaces information gain, not just parity. Boilerplate/nav headings are filtered out (pattern-class chrome filter). (v0.9.0; F6 fix v0.9.1, F1 generalized v0.9.2)
Every tool's tools/list entry carries the MCP standard annotations
(readOnlyHint, destructiveHint, idempotentHint, openWorldHint) so MCP
hosts can decide what to auto-approve and what to confirm.
Workflow prompts
The server publishes thirteen named MCP prompts (via prompts/list /
prompts/get) that chain the granular tools into common SEO workflows. Hosts
that surface prompts (Claude Desktop's slash menu, Cursor's command palette,
Cline's prompt picker) advertise them automatically.
Why prompts and not megatools: composability. A failed step inside a megatool poisons the megatool's envelope and the host loses the ability to retry just the failing leg. Prompts hand the host a recipe; each step's envelope arrives intact at the LLM.
Install
SEOMonster ships two install paths, both fully local:
.mcpbbundle for Claude Desktop. One-click install, GUI form for credentials, secret-typed inputs stored in the OS keychain. Recommended for most users.uvxfor Cursor, Cline, Codex, and Claude Desktop power users who prefer to hand-edit MCP config files.
Both paths run the same Python package (seo_mcp) and expose the same
52-tool surface. The difference is only how the host launches the server
and how it collects credentials.
Claude Desktop (recommended): .mcpb bundle
Three short steps. The OAuth consent is run once from a terminal (the GUI flow inside Claude Desktop's MCP subprocess times out before a real user can finish; see Why pre-flight auth? below).
1. Install the bundle. Download
seo-monster-0.2.0.mcpb
from GitHub releases (or, when listed, from the Claude
Directory) and double-click it. Claude Desktop
verifies the bundle, runs uv to materialize the Python environment, and
shows a configuration form:
Fill the fields, click Save, then toggle the extension on. Quit Claude Desktop completely (⌘Q on macOS) and reopen.
2. Run the one-time OAuth consent from a terminal. Before using any Google-backed tool, run:
A browser opens. Approve the requested scopes. The command writes
token.json to the path you configured (default ~/.config/seo-monster/token.json)
with 0600 permissions, then exits. This step is the recommended pattern; it
sidesteps the timeout that Claude Desktop imposes on every tool call.
3. Start a new chat in Claude Desktop and use the tools. Click the 🔧
tools icon in the input box; you should see 52 SEOMonster tools. Try
system_status first to verify everything is configured.
Why pre-flight auth?
The OAuth installed-app flow opens a local browser and waits for the user to
finish the consent screen. Inside Claude Desktop, MCP servers are launched as
subprocesses whose tool calls have a ~30-60 second timeout. Real users do not
complete browser consent that fast, so the originating call times out, and
since every Google tool retries the flow until a token exists, every call
times out in turn. Running uvx seo-monster auth once from a terminal puts
the token on disk; from that point on, Claude Desktop's MCP server just reads
the cached token and silently refreshes it as needed.
uvx for Cursor, Cline, Codex (and Claude Desktop power users)
uvx runs the published PyPI package seo-monster in an ephemeral
environment. Add the snippet for your host below, using the absolute path
to uvx (find it with which uvx; GUI hosts do not read your shell profile).
Cursor (~/.cursor/mcp.json or project .cursor/mcp.json)
Cline (cline_mcp_settings.json)
alwaysAllow lists read tools so Cline does not prompt on each call. Leave the
cache-purge tools off so they always prompt.
Codex (~/.codex/config.toml)
Claude Desktop, direct uvx (advanced)
If you prefer to hand-edit claude_desktop_config.json instead of using the
.mcpb bundle, the same snippet shape as Cursor above works.
Auth
The four services authenticate independently. Configure only the ones you use;
a tool for an unconfigured service returns a clear AUTH_MISSING error rather
than failing the server.
Quick setup (recommended): seo-monster setup
Run seo-monster setup once from a terminal. It interactively collects your
Cloudflare token, PageSpeed Insights key, IndexNow key, and the default GSC and
GA4 properties, validates what it can against the live APIs, and writes them to
~/.config/seo-mcp/config.toml with 0600 permissions. Your MCP host config
then needs no secrets in it:
Two things setup does not do, by design:
- Google OAuth still uses the separate one-time browser step. After
setup, runseo-monster authto complete Google consent (see the next section). - It never overrides environment variables. Anything set in your host's
envblock still wins over the config file, so CI and Docker keep using env vars.
setup is re-runnable: existing values are shown as defaults and kept when you
leave a field blank. The sections below document the per-service env vars, which
are what setup writes for you and what CI pipelines can set directly.
Google (Search Console + Analytics 4) - OAuth, recommended
This is the lower-friction path: no Cloud service account, no per-property email grants.
- In the Google Cloud Console, create (or
pick) a project and enable the APIs you will use:
- Search Console API
- Indexing API (for
gsc_request_indexing) - Google Analytics Data API (for the GA4 tools)
- PageSpeed Insights API (only if you want a PSI key; see below)
- Create an OAuth client of type Desktop app and download the client-secrets JSON.
- Point the server at it and at a writable token path:
SEO_MCP_GOOGLE_OAUTH_CLIENT= path to the client-secrets JSONSEO_MCP_GOOGLE_TOKEN= a writable path where the token will be cached
- One-time: run
uvx seo-monster authfrom a terminal. A browser opens; approve the scopes. The command writestoken.json(0600) and exits. - Subsequent runs (server-side) refresh the token silently. The server
never opens a browser; if the cached token is missing, tools return
AUTH_MISSINGpointing back at theauthcommand.
The signed-in Google account must have access to the Search Console properties and GA4 properties you query.
Token-cache hardening. The cached token is refresh-capable and equivalent
to a long-lived credential for the requested scopes. The server writes it with
0600 and its parent directory with 0700. Keep SEO_MCP_GOOGLE_TOKEN under
a directory you control (e.g. ~/.config/seo-monster/) and do not put it on a
shared filesystem.
Google - service account (advanced, headless)
For fully headless or server deployments where a browser is not available:
- Create a service account and download its JSON key.
- Set
SEO_MCP_GOOGLE_CREDENTIALS(or the standardGOOGLE_APPLICATION_CREDENTIALS) to the key path. - Grant the service-account email access on each property:
- Search Console: add it as a user on the property.
- GA4: add it as a Viewer on the property.
If both OAuth and a service account are configured, OAuth is used.
Coverage note. The OAuth installed-app path is exercised in our validation pass and in production-style smoke tests. The service-account path is documented but not independently validated against a live Cloud project. If you hit issues on the SA path, please open an issue.
Scopes (minimal vs full)
The default consent requests the scopes needed for every tool, including the two writes:
If you only want reads, you can consent to a narrower set
(webmasters.readonly + analytics.readonly) and simply not call
gsc_submit_sitemap / gsc_request_indexing; calling a write tool without its
scope returns SCOPE_INSUFFICIENT with remediation, never a crash.
PageSpeed Insights
PSI works without a key in principle, but in practice the anonymous quota is
shared across every caller without a key and is frequently exhausted: a
single psi_analyze call against the anonymous endpoint often returns
RATE_LIMITED. Treat the anonymous mode as a fallback, not the steady
state.
To get reliable PSI access:
- In Cloud Console, enable the PageSpeed Insights API.
- Create an API key (Credentials > Create credentials > API key). It takes a minute. The key is free.
- Set
PSI_API_KEY(or use the field in the.mcpbconfiguration form).
The PSI API only accepts the key as a URL query parameter (not a header), so treat PSI keys as low-sensitivity. Scope the key to the PageSpeed Insights API only and attach no other GCP roles.
Cloudflare
Create an API token at
dash.cloudflare.com/profile/api-tokens
and set CF_API_TOKEN (and optionally CF_ZONE for a default zone). Grant only
the permissions you need:
IndexNow
IndexNow notifies Bing, Yandex, Naver, Seznam, and Yep when a URL is created
or updated. Google does not participate, so the IndexNow tools complement
rather than replace gsc_request_indexing.
One-time setup
- Generate a key. Any 8-128 character string of letters, digits, or
hyphens (
a-z,A-Z,0-9,-) per the IndexNow spec. Common patterns: a 32-char lowercase hex string (e.g.python -c "import secrets; print(secrets.token_hex(16))") or any random alphanumeric of similar length. Treat it like an API key; do not commit it. - Configure SEOMonster by setting
SEO_MCP_INDEXNOW_KEYto that string (or use the.mcpbconfiguration form; the field is marked sensitive and lands in the OS keychain). - Host the verification file at
https://<your-host>/<key>.txt. The file body MUST be exactly the key string with no trailing newline, no BOM, no extra whitespace, no HTML wrapper. The Content-Type should betext/plain. Confirm withcurl -i https://<your-host>/<key>.txtbefore moving on; the response body must be byte-identical to the key. - (Optional) Set
SEO_MCP_INDEXNOW_KEY_LOCATIONif the verification file lives at a non-standard URL (some CDNs rewrite/key.txtpaths). The default location ishttps://<host>/<key>.txtderived from the URLs you submit, so you usually do not need this.
Same-host constraint
Every URL submitted in one indexnow_submit or indexnow_bulk_submit call
must share the same host as the verification file. Mixed-host batches are
rejected by IndexNow with HTTP 422; indexnow_bulk_submit enforces this
client-side and returns INVALID_INPUT before any network call when it
detects mixed hosts.
If you have multiple hosts, host a verification file per host and either
make separate calls per host or override SEO_MCP_INDEXNOW_KEY_LOCATION
per call (the tool does not currently expose per-call override; set
distinct env values per session).
Common errors
Verify your setup
After configuring, call system_status to see what is detected. Call it with
{"probe": true} to make one cheap live request per configured service and
confirm the credentials actually work (GSC lists properties, GA4 runs a 1-row
report against the default property, Cloudflare lists one zone, PSI pings the
endpoint). With probe off (the default) it does a config-only check and makes
no network calls.
Destructive mode
Cache purges affect every visitor, so they are off by default. Set
SEO_MCP_ALLOW_DESTRUCTIVE=true to enable cf_purge_cache and
cf_purge_cache_all. While off, those tools return DESTRUCTIVE_DISABLED and
make no network call.
cf_purge_cache_all (purge the whole zone) carries an extra safeguard: it
requires a confirm argument equal to the resolved zone hostname. A missing or
mismatched confirm returns CONFIRM_REQUIRED and issues no purge.
The two GSC writes (gsc_submit_sitemap, gsc_request_indexing) are not
gated; they are routine, low-blast-radius SEO tasks.
Configuration
Resolution is environment-first, with a TOML file fallback. Environment always
wins. The config file is normally written for you by seo-monster setup (with
0600 permissions); you can also write it by hand or set the env vars below.
Config file fallback at ~/.config/seo-mcp/config.toml (or SEO_MCP_CONFIG):
Result envelope
Every tool returns the same shape. On success:
On failure:
Error codes:
Development
The package exposes two console-script aliases: seo-monster (canonical,
matches the PyPI distribution) and seo-mcp (a v0.1.x dev alias kept for
back-compat). Both invoke the same entry point. As of v0.2.0, invoking the
server via seo-mcp emits a one-line stderr deprecation notice; nothing on
stdout, so the MCP protocol channel is unaffected. Production configs should
use seo-monster; the alias will be removed in a future major release.
Tests are fully offline: they mock at the client layer, so no network and no credentials are needed to run them.
Server identity note. Some MCP host UIs display the server name as
seo-mcpand the version as themcpSDK version (e.g.1.27.1). The server-name string is the value we passed toServer("seo-mcp")and is kept stable for back-compat; the version readout is a quirk of the SDK (create_initialization_options()does not propagate the package version). The package's real version is inpyproject.tomlandseo_mcp.__version__.
Changelog
Release-by-release notes, including the validation checks each version's external testing pass should cover, live in CHANGELOG.md.
Privacy
SEOMonster runs entirely on your machine and talks only to the upstream APIs you configure. The maintainers do not see any of your data, credentials, queries, or tool calls. See PRIVACY.md for the full statement.
License
MIT. See LICENSE.
来源:README.md,提交 6b727c1
工具
0版本历史
2- v0.9.3最新Sep 26, 2026
- v0.5.1Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分