Skip to content
Agentmart
Submit a tool

SEO Monster vs SEO Skill

SEO Monster and SEO Skill are both MCP servers for SEO. SEO Monster is published by avansaber and SEO Skill by seoskill.dev (the vendor). SEO Monster runs locally (stdio), while SEO Skill runs locally (stdio) and as a remote server (HTTP). SEO Monster lists installs for Claude Code, Codex, VS Code and Cursor; SEO Skill for Claude Code, VS Code, Codex and Cursor. On GitHub, SEO Skill has 593 stars and SEO Monster has 553. SEO Monster was last active in Sep 2026, SEO Skill in Oct 2026. The table lines up where they differ (publisher, official vendor, license and runs) and has the install commands for both. Everything here comes from the listings' public sources and is refreshed daily. SEO Monster describes itself as: Local-first SEO MCP: track AI citations, Search Console, GA4, PageSpeed, Cloudflare, IndexNow, CrUX.

Updated Oct 26, 2026 · Built from catalog data; how we rank and grade

Who should pick which

  • Pick SEO Skill if you want a remote server with nothing to install locally.
  • Pick SEO Skill if you prefer the vendor's own MCP server.

From listing data only. We don't pick a winner on security beyond the grades; read how grades work.

Side by side

FactSEO MonsterSEO Skill
TypeConnectorConnector
Publisheravansaberseoskill.devOfficial
LicenseMITApache-2.0
PricingNot statedNot stated
RunsLocal (stdio)Local (stdio), Remote (HTTP)
AuthAPI keyAuth not stated
Hosts supportedClaude Code, Codex, VS Code, Cursor, Windsurf, Claude DesktopClaude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop
Tools6639
Security grade–Security: not graded yet–Security: not graded yet
Freshness gradeAFreshness: AAFreshness: A
GitHub stars553593
Weekly downloads313Not measured
Last releaseSep 25, 2026Oct 16, 2026
Last activitySep 25, 2026Oct 23, 2026

Facts from each listing's public sources, checked daily. Tool lists arrive with tool scans.

Install

SEO Monster

claude mcp add seo-monster -- uvx seo-monster@0.9.3

Settings it needs

  • SEO_MCP_GOOGLE_OAUTH_CLIENT · Path to your Desktop-app OAuth client-secrets JSON, downloaded from Google Cloud Console. Required for Search Console, Indexing, and GA4 tools.
  • SEO_MCP_GOOGLE_TOKEN · Writable path where the cached OAuth token is stored. On first use, a browser opens for one-time consent and the token is written here. Default: ${HOME}/.config/seo-monster/token.json
  • SEO_MCP_GSC_DEFAULT_SITE · Default Search Console property, e.g. 'sc-domain:example.com' or 'https://www.example.com/'.
  • SEO_MCP_GA4_PROPERTY_ID · Default GA4 property, e.g. 'properties/123456789' or bare '123456789'.
  • PSI_API_KEYsecret · Google API key shared by PageSpeed Insights and Chrome UX Report History tools. Optional; both work anonymously at a tighter rate limit when unset.
  • CF_API_TOKENsecret · Cloudflare API token. Optional; needed only for the Cloudflare tools. Scopes: Zone:Read, DNS:Read, Account Analytics:Read, and (only when destructive mode is on) Cache Purge:Purge, Single Redirect:Edit, Zone Settings:Edit, and (for bulk redirects) Account Rulesets:Edit + Account Filter Lists:Edit.
  • CF_ZONE · Default Cloudflare zone hostname, e.g. 'example.com'.
  • SEO_MCP_INDEXNOW_KEYsecret · IndexNow shared key (any 8-128 hex string you generate). Required only for the IndexNow tools. Host the key file at https://<your-host>/<key>.txt for engine verification.
  • SEO_MCP_INDEXNOW_KEY_LOCATION · Override the default IndexNow key-file URL (https://<host>/<key>.txt). Set only if you host the key file at a non-standard path.
  • SEO_MCP_ALLOW_DESTRUCTIVE · Set to 'true' to enable the Cloudflare cache-purge tools. Default false: all destructive tools refuse to run.
  • DATAFORSEO_LOGINsecret · DataForSEO Basic-auth login. Optional (v0.9). Unlocks SERP/PAA/related, keyword volume+difficulty+intent, competitor keyword-gap, and Google AI Overview citations for keyword_universe / serp_adjacency_expand / onpage_serp_gap auto-fetch / ai_citation_track.
  • DATAFORSEO_PASSWORDsecret · DataForSEO Basic-auth password. Optional (v0.9). Required alongside DATAFORSEO_LOGIN.
  • OPENPAGERANK_API_KEYsecret · Open PageRank (DomCop) free API key. Optional (v0.9). Free competitor domain-authority proxy for onpage_serp_gap.
  • PERPLEXITY_API_KEYsecret · Perplexity Sonar API key. Optional (v0.9). One of the AI answer-engines for ai_citation_track.
  • OPENAI_API_KEYsecret · OpenAI API key (Responses web_search). Optional (v0.9). One of the AI answer-engines for ai_citation_track.
  • ANTHROPIC_API_KEYsecret · Anthropic API key (web_search tool). Optional (v0.9). One of the AI answer-engines for ai_citation_track.
  • GEMINI_API_KEYsecret · Google Gemini API key (Search grounding). Optional (v0.9). One of the AI answer-engines for ai_citation_track.
  • GOOGLE_ADS_DEVELOPER_TOKENsecret · Google Ads API developer token. Optional (v0.9). Volume-only alternative to DataForSEO for keyword_universe; live use also needs an adwords-scope OAuth re-consent.
  • GOOGLE_ADS_CUSTOMER_ID · Google Ads customer id (digits). Optional (v0.9). Required alongside GOOGLE_ADS_DEVELOPER_TOKEN.

SEO Skill

claude mcp add --transport http seo https://seoskill.dev/mcp

Also consider

Questions

Is SEO Monster or SEO Skill more popular?
SEO Skill has more GitHub stars (593 against 553). Stars measure attention, not quality, so check freshness and docs too.
Do SEO Monster and SEO Skill work with Claude Code?
Yes, both list a Claude Code install; the commands are on this page.
Which one runs without a local install?
SEO Skill offers a remote endpoint; SEO Monster runs locally.
Cite this page

SEO Monster vs SEO Skill. Agent Mart. https://agentmart.dev/compare/avansaber-seo-monster-vs-seoskill-dev-seo (last updated 2026-10-26)