Skip to main content
Glama
pabsamuel

SEO Data MCP

by pabsamuel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to SEO Data MCP

No user-submitted related servers found.

    Related Servers

    • @lomi./gsc-mcp

      lomiafrica
      A
      license
      B
      quality
      B
      maintenance
      Enables Google Search Console data queries via MCP, including search analytics, performance comparisons, URL inspection, and sitemap management.
      12
      1
      MIT

    • mcp-server-google-search

      thein-art
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Google Search Console via MCP, offering search analytics, performance summaries, URL inspection, sitemap management, and property listing for SEO workflows.
      110 npm
      1
      MIT

    • GSC MCP Server

      soumyadeep-ux
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Google Search Console to query search analytics, inspect URL indexing status, and manage sitemaps. It allows users to monitor SEO performance and site health through natural language commands in MCP-compatible clients.
      148 npm
      3
      MIT

    • seomcp

      davide-cik
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude and other MCP clients to read Google Search Console and Bing Webmaster Tools data, analyze query/page performance, compare periods, inspect indexing and canonical status, and retrieve sitemap and keyword statistics.
      23
      1,295 npm
      MIT

    • GSC MCP Server

      luminarylane
      A
      license
      A
      quality
      A
      maintenance
      Connects MCP clients to the Google Search Console API, enabling search analytics queries, URL inspection, sitemap management, and performance comparison across time periods.
      20
      54 PyPI
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct SEO data source or operation: GSC querying, GSC inspection, GSC sitemaps, Bing stats, Bing crawl issues, IndexNow submission, PageSpeed, and CrUX. The read-only tools are separated from the explicit write tool, and performance tools are split into lab (PageSpeed) versus field (CrUX) data.

    Naming Consistency3/5

    Most names use snake_case and a service_action pattern (gsc_query, bing_query_stats, indexnow_submit), which is readable. However, pagespeed and crux are bare product names with no verb, and action placement varies across prefixes, so the set is mixed rather than fully consistent.

    Tool Count5/5

    Eight tools is well-scoped for an SEO data server, covering the main integrations without obvious padding. Each tool corresponds to a meaningful data source or action.

    Completeness4/5

    The surface covers key SEO data sources: GSC performance, inspection, sitemaps, Bing stats and crawl issues, IndexNow submission, PageSpeed, and CrUX. Minor gaps remain, such as sitemap submission/management and broader keyword or backlink data, but core read and submission workflows are present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources