MaxAEO AI Visibility MCP Server

Local-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits.

Remote serverstreamable-http

What is the MaxAEO AI Visibility MCP MCP server?

MaxAEO AI Visibility MCP MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Local-first MCP server for AI visibility, GEO/AEO, llms.txt, and AI crawler readiness audits.

What you get

Local-first Model Context Protocol (MCP) server for AI visibility audits, GEO, AEO, AI SEO, llms.txt, and AI crawler readiness in Claude, Codex, Cursor, Windsurf, and other MCP-compatible agents.

What the assistant can call

Once MaxAEO AI Visibility MCP is connected, these are the calls the assistant has available:

  • check_llms_txt — Validate /llms.txt, linked URLs, robots alignment, and sitemap alignment
  • audit_ai_crawler_readiness — Check robots rules, sitemap availability, homepage metadata, canonical, schema, and AI crawler access basics
  • build_ai_visibility_report — Run the local checks and return a concise action plan with MaxAEO CTA
  • locale — en-US, en, global, zh-CN, zh, cn
  • market — global, cn
  • ctaBaseUrl — URL

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

This sits in the search and retrieval group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MaxAEO AI Visibility MCP's toolset — check_llms_txt, audit_ai_crawler_readiness, build_ai_visibility_report and 3 more — is a fair guide to whether it matches your workflow. It is maintained by maxaeo; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MaxAEO AI Visibility MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the maxaeo ai visibility mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
check_llms_txtValidate /llms.txt, linked URLs, robots alignment, and sitemap alignment.
audit_ai_crawler_readinessCheck robots rules, sitemap availability, homepage metadata, canonical, schema, and AI crawler access basics.
build_ai_visibility_reportRun the local checks and return a concise action plan with MaxAEO CTA.
localeen-US, en, global, zh-CN, zh, cn
marketglobal, cn
ctaBaseUrlURL

How to install the MaxAEO AI Visibility MCP MCP server

Add to an MCP client:

```json
{
  "mcpServers": {
    "maxaeo-ai-visibility": {
      "command": "npx",
      "args": ["-y", "maxaeo-ai-visibility-mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use MaxAEO AI Visibility MCP to check llms txt.
  • Use MaxAEO AI Visibility MCP to audit ai crawler readiness.
  • Use MaxAEO AI Visibility MCP to build ai visibility report.

Frequently asked questions

It connects MaxAEO AI Visibility MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (check_llms_txt, audit_ai_crawler_readiness, build_ai_visibility_report, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MaxAEO AI Visibility MCP directly.