ai-visibility-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDFLARE_API_KEY | No | Global API key for Cloudflare API authentication. Only needed for cloudflare_ai_bot_audit. | |
| CLOUDFLARE_API_EMAIL | No | Email address for Cloudflare API authentication. Only needed for cloudflare_ai_bot_audit. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_visibilityA | Check a site's actual AI-crawler visibility: fetch its live robots.txt and look for Disallow rules blocking named AI bots (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, etc.) or a wildcard block, plus whether llms.txt actually exists as a real file (vs. falling through to a SPA catch-all). |
| cloudflare_ai_bot_auditA | Read a Cloudflare zone's Bot Management AI-bot settings (ai_bots_protection, ai_training, ai_search, ai_user, is_robots_txt_managed) for a domain. Requires CLOUDFLARE_API_EMAIL and CLOUDFLARE_API_KEY env vars (Global API Key, X-Auth-Email/X-Auth-Key auth). |
| generate_llms_txtA | Generate an llms.txt line plus a content pack (ownable phrase, llms.txt sentence, meta description, FAQ block) for a product, ready to hand-place on a landing page or drop as a file. Does not write files or touch git — pure text generation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: one checks live robots.txt and llms.txt, one audits Cloudflare's specific AI bot settings, and one generates llms.txt content. There is no overlap or ambiguity.
All names use snake_case and include a verb, but check_visibility and generate_llms_txt follow a verb_noun pattern while cloudflare_ai_bot_audit places the verb at the end of a compound noun. This slight inconsistency is minor and does not hinder readability.
Three tools is a reasonable number for a focused domain like AI crawler visibility. The scope is narrow enough that each tool earns its place without feeling sparse or excessive.
The tool set covers the core workflows: checking visibility, auditing a specific provider's settings, and generating content. However, it lacks support for other hosting providers beyond Cloudflare and does not include any write/modify capabilities, which may be expected in a visibility management server but is likely intentional as an analysis-only tool.