MCP.Market

AI SEO MCP server

by AutomateLab-tech·io.github.AutomateLab-tech/ai-seo·v0.1.1·3 stars

MCP server for AI-SEO auditing: schema, robots.txt, llms.txt, citation scoring, and AEO/GEO rewrites

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

3 stars

Reviews

Write one

Nobody has reviewed AI SEO yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AI SEO tools (13, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit_canonical

    Audit canonical link integrity, trailing-slash hygiene, self-referencing, and og:url consistency.

  • audit_pagewrite action

    Run a full AI-SEO audit on a single URL and return categorized findings with severity, fix instructions, and a 0-100 score.

  • audit_schema

    Validate JSON-LD structured data on a URL or raw JSON string against Schema.org rules and AI-citation best practices.

  • check_robots

    Parse a domain's robots.txt and report per-crawler allow/disallow posture for all known AI crawlers.

  • check_sitemap

    Validate a domain's XML sitemap for presence, accessibility, URL count, lastmod freshness, and AI-search attributes.

  • check_technical

    Audit a page's HEAD for canonical, OpenGraph, Twitter Card, hreflang, HTTPS, noindex, and title hygiene.

  • extract_entities

    Extract named entities, linked concepts, and sameAs graph nodes from a page's content and structured data.

  • generate_llms_txt

    Generate a valid llms.txt (and optionally llms-full.txt) for a domain from its sitemap.

  • rewrite_for_aeo

    Rewrite a content block for Answer Engine Optimization - adds BLUF opening, FAQ structure, and schema additions.

  • rewrite_for_geo

    Rewrite a content block for Generative Engine Optimization - entity-rich, comparison-ready, synthesis-friendly.

  • score_ai_overview_eligibility

    Score a page's probability of appearing in Google AI Overviews using published 2025-2026 correlation factors.

  • score_citation_worthiness

    Score how citable a page or text block is for AI engines: BLUF, FAQ patterns, statistic density, entity clarity.

  • validate_llms_txt

    Validate an existing llms.txt or llms-full.txt against the spec, checking structure and broken links.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan51 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 111 days ago8/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How AI SEO compares

Against every graded SEO MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 63% of 769 SEO servers
Tools
13
the typical SEO server has 6
Tools that change things
8%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
3
more than 80% of 400 SEO servers

What its tools let an agent do: 11 read · 1 create · 1 change

Install AI SEO in Claude Code, Cursor or VS Code

Runs npx -y @automatelab/ai-seo-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ai-seo -- npx -y @automatelab/ai-seo-mcp
Add to Cursor

What the publisher says

From the AI SEO repository's README, as published. We do not edit it. Read it on GitHub

@automatelab/ai-seo-mcp

AI Citation Toolkit for the Model Context Protocol

Audit why AI systems do or do not cite your pages. MCP server. No API keys.

Works inside Claude, Cursor, Windsurf, Codex, and any MCP client that speaks stdio.

What it checks

  • AI crawler access - GPTBot, OAI-SearchBot, ClaudeBot, and PerplexityBot allowed or blocked in robots.txt
  • llms.txt - present, spec-compliant, links alive
  • Structured answer extraction - FAQ headings, BLUF paragraphs, answer-ready blocks
  • [[schema]] completeness - FAQPage, Article, Organization, Person; flags deprecated patterns
  • Entity clarity - named entity density and sameAs coverage that help AI systems identify the subject
  • Citation formatting - canonical URL hygiene, og:url, hreflang, noindex traps
  • Sitemap freshness - lastmod signals that tell crawlers the page is current

Run an audit. Get a list of citation-blockers, ranked.

You: Run an AI-SEO audit on https://automatelab.tech/launching-the-ai-seo-mcp/.

Result (truncated):

{
  "url": "https://automatelab.tech/launching-the-ai-seo-mcp/",
  "score": 61,
  "grade": "C",
  "dimension_scores": {
    "schema": 45, "technical": 80, "structure": 40,
    "robots": 90, "freshness": 85, "authority": 40,
    "entity_density": 21, "sitemap": 100
  },
  "findings": [
    {
      "severity": "critical",
      "category": "structure",
      "message": "No FAQ structure found (no FAQPage schema or H3 question headings).",
      "fix": "Add FAQ H3 headings ending in '?' with answer paragraphs, and a FAQPage JSON-LD block.",
      "estimated_impact": "high"
    },
    {
      "severity": "warning",
      "category": "authority",
      "message": "Low authority signals - missing Organization or author Person schema.",
      "fix": "Add Organization JSON-LD and Article.author as a Person node with sameAs links.",
      "estimated_impact": "high"
    }
  ]
}

Each finding names the exact fix. No opaque scores, no guesswork.

Install

npx -y @automatelab/ai-seo-mcp

Requires Node 20 or later.

Claude Desktop

Add to %APPDATA%\Claude\claudedesktopconfig.json (Windows) or ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS):

{
  "mcpServers": {
    "ai-seo": {
      "command": "npx",
      "args": ["-y", "@automatelab/ai-seo-mcp"]
    }
  }
}

Restart Claude Desktop. Any MCP client that supports stdio transport works - same command / args pattern.

Optional: headless rendering for SPAs

By default audit_page reads raw HTML — fast, but misses content on React/Vue/Angular SPAs. Pass render: "headless" to spin up Chromium and audit the rendered DOM (adds 3-10s per audit).

One-time install:

npm install playwright-core
npx playwright install chromium

Then call audit_page with render: "headless". Use static for everything else — most marketing sites and docs render fine without it.

Run it in CI (GitHub Action)

This repo doubles as a GitHub Action. Drop it in a workflow to fail a PR when any page regresses below an AI-citation score - the same audit engine, gated on every change.

- uses: actions/checkout@v4
- name: AI-SEO audit
  uses: AutomateLab-tech/ai-seo-mcp@v0.5.0
  with:
    urls: "https://example.com,https://example.com/pricing"
    min-score: "70"            # fail if any URL scores below this
    respect-robots: "true"     # set false for staging / sites you own
    report-path: "ai-seo-report.md"   # optional Markdown report artifact
    fail-on-regression: "true"

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

AI SEO: common questions

Is AI SEO MCP server safe?
Mostly: it is graded B (80/100). Read the AI SEO safety report
How do I install AI SEO?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does AI SEO need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is AI SEO maintained?
The last commit was 147 days ago (2026-06-08). The latest release is v0.1.1.
What can I use instead of AI SEO?
Servers from other publishers that do the same job: geoseo-mcp server, SEO & GEO MCP server and Google Ads + Meta Ads + SEO/GEO MCP server.
How does AI SEO compare with other SEO MCP servers?
safety score 80/100 (higher than 63% of 769 SEO servers); tools 13 (the typical SEO server has 6); tools that change things 8% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to AI SEO

Same job from other publishers: the closest match first, then the best rated.

  • geoseo-mcp
    SEO + GEO: Search Console, Bing, Yandex, IndexNow, AI Overviews and LLM citation tracking.
    B
  • SEO & GEO
    Audit a page's SEO and its readiness for AI answer engines: meta, schema, robots, sitemaps, AI bots.
    A
  • Google Ads + Meta Ads + SEO/GEO MCP
    Google Ads, Meta Ads, Google Analytics (GA4) & Search Console MCP server by Ryze AI
    A
  • SEO Monster
    Local-first SEO MCP: track AI citations, Search Console, GA4, PageSpeed, Cloudflare, IndexNow, CrUX.
    A
  • RankCLI
    Free, local SEO + GEO audits for AI assistants - no signup, nothing leaves your machine.
    A

More from AutomateLab-tech →