Skip to main content
Glama
ibrahimhajjaj

seo-console-mcp

by ibrahimhajjaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to seo-console-mcp

No user-submitted related servers found.

    Related Servers

    • gsc-mcp

      FlorianBruniaux
      A
      license
      B
      quality
      A
      maintenance
      MCP server providing 32 tools for Google Search Console and Google Analytics 4, enabling search analytics, URL inspection, indexing, and cross-platform analysis via natural language.
      43
      36 PyPI
      12
      MIT

    • gsc-mcp

      jayrockliffe-defused
      A
      license
      A
      quality
      C
      maintenance
      MCP server for querying Google Search Console data — search analytics, URL inspection, sitemap monitoring, and more — read-only tools for any MCP-compatible AI client.
      7
      Apache 2.0

    • mcp-seo-audit

      GiorgiKemo
      A
      license
      B
      quality
      B
      maintenance
      SEO audit and Google Search Console MCP server with 23 tools. Search analytics, URL inspection, Indexing API, Core Web Vitals (CrUX), striking distance keywords, keyword cannibalization detection, branded query analysis, and automated site audits.
      30
      2
      MIT

    • AppScope MCP Server

      Ahad690
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP server for app market intelligence, enabling tools to query app download/revenue estimates, ad intensity proxies, creator mentions, and rank history from local collected data.
      MIT

    • mcp-store-scraper

      LucasMonteiro1
      A
      license
      B
      quality
      C
      maintenance
      MCP server that scrapes app data from Google Play and Apple App Store, providing tools for search, details, reviews, and similar apps.
      8
      15 npm
      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 43 tools

    Disambiguation3/5

    Most tools target distinct surfaces (Search Console, App Store, Play, Ads, CRUX), and the detailed descriptions separate near neighbors like ctr_gaps and search_opportunities. However, clusters such as seo_audit/audit_site, ads_ads/ads_ad_copy, and the six search-analytics tools still create real selection risk, so the set is not fully unambiguous.

    Naming Consistency4/5

    The dominant pattern is snake_case verb_noun (list_sitemaps, submit_sitemap, ads_update, crux_field_data), and write tools consistently signal side effects. A notable minority uses noun-only or phrase names (keyword_ideas, search_opportunities, ctr_gaps, query_cannibalization, compare_search_periods), breaking the pattern enough to lower consistency.

    Tool Count2/5

    43 tools is far beyond the 3–15 sweet spot for a single server. The count is inflated by parallel surfaces (Search Console, App Store, Play, Ads, snapshots) and numerous analytics slice tools, which makes the server feel like a bundled suite rather than a focused console.

    Completeness4/5

    The set covers an unusually wide lifecycle: sitemap management, index inspection, search analytics, page audits, app-store/Play reads, ads reads and guarded writes, plus snapshot comparison. Gaps are minor—no Search Console property add/remove and no ad campaign or ad-group creation—but most workflows reach a terminal action.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources