← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionSEO Skill MCP ServerA local-first SEO command line and MCP server for AI agents, running 70+ audit tools on your own crawl, Search Console, and GA4 data.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS64 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions13 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Site owners who want a clear audit and a ranked fix list without learning a heavy dashboard
  • AI agents that need real crawl, Search Console, analytics, keyword, and competitor evidence through MCP
  • Developers who want to embed the same report engine in a script, CI job, or TypeScript app
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users expecting a hosted dashboard or cloud data storage — data stays on the local machine
  • Users needing official endorsement from Google or an SEO vendor — the project is third-party maintained
  • Users without a Node 22+ runtime
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Read the local config directory to store project profiles, crawl reports, and provider caches
  • Access the system keychain for Google OAuth tokens, Bing API key, IndexNow key, and similar credentials, falling back to a private 0600 file
  • Network requests to audited sites, Google Search Console, Google Analytics, Bing Webmaster, Clicky, and selected research providers when enabled
  • Optional access to Chrome UX Report, IndexNow, and the npm registry
  • Optional CI use of a Google service account JSON key and environment variables such as SEO_GOOGLE_SERVICE_ACCOUNT_JSON, SEO_BING_API_KEY, SEO_CLICKY_SITEKEY, and SEO_INDEXNOW_KEY
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Optional external enrichment can send selected Search Console query or derived seed text to the chosen research provider only when explicitly enabled; it does not send Google credentials, property IDs, Search Console metrics, or Google Analytics rows
  • When the system keychain is used, processes that cannot access it may read credentials readable by the same process user; without a keychain the CLI falls back to a private local file
  • Research providers can charge for API requests; reports show estimated and actual cost, but spend limits are your responsibility
  • Crawling issues many requests to the target site and may trigger access blocks; the report retains HTTP status, provider indicators, and access guidance
  • User-agent names can be spoofed, so the server-log report describes request strings found in the log rather than verified crawler identity
  • An accepted IndexNow request confirms receipt only and does not prove a URL was crawled, indexed, ranked, or shown
  • Provider traffic, volume, difficulty, and visibility values are estimates and are not search-engine measured data
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsCodex, Claude Code, Claude Desktop, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools40