Skip to main content
Glama

Related Servers

Alternatives to seodata-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Provides on-page SEO analysis via MCP tools, including page audits, schema extraction, robots.txt checks, sitemap parsing, and link analysis. No API keys required; works with any MCP-compatible client.
      5
      6 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Checks a website's AI readiness: can ChatGPT, Claude, Perplexity, Google AI and 50+ other AI crawlers (GPTBot, ClaudeBot, PerplexityBot) access it? Scores the site, then generates llms.txt, an AI-crawler robots.txt and JSON-LD, and reads LLM Monitor trends, from Claude Desktop, Cursor and other MCP clients.
      8
      206 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables calling 120+ AI models and reading live web pages (scrape, crawl, structured extract) from any MCP client using one API key.
      9
      40 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI agents in Cline, Claude, or Cursor to a hosted SEO data service so they can query Search Console performance, keywords, backlinks, competitors, and AI-visibility insights for a connected site, as well as stage SEO fixes, campaigns, and article drafts that require human approval before going live.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language, read-only analysis of your own Google Search Console and Google Analytics 4 data, including search performance, engagement, sitemap health, ranking opportunities, and deterministic SEO audits through MCP clients like ChatGPT.
      MIT

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool has a largely distinct purpose: identity check, storefront listing, article listing/retrieval, page retrieval, search, audit, generation, job status, and positions. There is minor overlap between seodata_list_articles (returns full content) and seodata_get_article, and seodata_search partially overlaps with listing, but the descriptions clarify scope adequately.

    Naming Consistency4/5

    Nearly all tools follow a consistent seodata_verb_noun snake_case pattern (list_storefronts, get_article, run_audit, generate_article, get_job, get_positions). Only seodata_whoami deviates, being a bare noun-style identifier rather than verb_noun, but overall the convention is highly predictable.

    Tool Count5/5

    Ten tools is well within the ideal 3-15 range and each one maps to a concrete operation (auth, listing, retrieval, search, audit, generation, jobs, positions). No redundant or filler tools are present.

    Completeness4/5

    The read-oriented SEO/content surface is well covered: auth, storefronts, articles, pages, search, audits, AI generation, async jobs, and position tracking. Minor gaps exist—there's no explicit article update/delete or keyword management, and audit history retrieval isn't exposed—but core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues