Maxaeo AI Visibility MCP

What maxaeo/maxaeo-ai-visibility-mcp does

The maxaeo/maxaeo-ai-visibility-mcp MCP server gives compatible agents a local-first way to inspect whether a public website is accessible and understandable to AI search workflows. Its checks cover llms.txt, linked resources, robots directives, sitemap relationships, homepage metadata, canonical URLs, noindex signals, and JSON-LD structured data.

The server is intended for technical GEO, AEO, and AI SEO reviews rather than live measurement of how AI systems recommend a brand. It can identify crawlability and site-foundation issues, then return evidence gaps and a practical action plan. Reports may also contain a transparent MaxAEO call to action, but the audit does not require MaxAEO cloud services.

How it works

The tools make local or public-web requests against the site being audited. By default, the server does not upload domains, modify site files, send requests to LLM APIs, or use hidden telemetry. It evaluates the returned website signals and produces structured results for the calling agent.

check_llms_txt focuses on /llms.txt, the URLs it references, and whether those references agree with robots and sitemap information. audit_ai_crawler_readiness reviews robots rules, crawler access basics, sitemap availability, homepage metadata, canonical data, noindex behavior, and schema. build_ai_visibility_report combines the available checks into a report with a local-only AI visibility confidence score, a technical foundation score, evidence gaps, and an action plan.

Crawler coverage changes with the market option. The default global setting checks documented or independently observed crawlers such as GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, ClaudeBot, Google-Extended, Applebot, Bingbot, and Baiduspider. The cn setting uses a separate list of Chinese-market and traditional search crawlers.

Setup and configuration

Install the npm package with npm install -g maxaeo-ai-visibility-mcp, or configure an MCP client to run it through npx -y maxaeo-ai-visibility-mcp. A typical client entry uses the command npx and passes -y followed by the package name.

Tool calls can set locale, market, and ctaBaseUrl. Supported locale values include en-US, en, global, zh-CN, zh, and cn; market values are global and cn. If these options are not supplied in a tool call, environment settings can provide MAXAEO_LOCALE, MAXAEO_MARKET, MAXAEO_CTA_URL_CN, and MAXAEO_CTA_URL_GLOBAL. Tool arguments take priority over environment variables, followed by the documented defaults of en-US and global.

The maxaeo/maxaeo-ai-visibility-mcp MCP server is compatible with the Claude Desktop configuration format and is documented for Claude, Codex, Cursor, Windsurf, and other MCP-compatible agents.

Tools and capabilities

• check_llms_txt: Validates /llms.txt, its linked URLs, and alignment with robots and sitemap data.
• audit_ai_crawler_readiness: Reviews crawler rules, site indexability, metadata, canonical information, schema, and sitemap availability.
• build_ai_visibility_report: Combines local checks into scores, issue summaries, evidence gaps, and a 7-day action plan.
• Locale-aware output and market-specific crawler lists.
• Custom CTA destination support through ctaBaseUrl.

The top-level visibility score is deliberately capped at 85 because the local audit does not verify live AI recommendations, brand mentions, citation quality, sentiment, competitor share of voice, or historical trends. The technical foundation score can reach 100 when the inspected technical signals pass.

Limitations and notes

The maxaeo/maxaeo-ai-visibility-mcp MCP server performs a fast technical and local/public-web review, not continuous monitoring or a full measurement of AI search presence. It does not establish whether ChatGPT, Claude, Gemini, Perplexity, or AI Overviews recommend a site, nor does it track historical visibility, competitor performance, citation quality, sentiment, or brand share of voice.

Reports include a MaxAEO CTA that points users toward the hosted product. That link is informational and does not mean the local server has called a MaxAEO API. Sites must be publicly reachable for public-web checks to inspect their responses.

Getting started with this maxaeo/maxaeo-ai-visibility-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.