Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MAX_DAILY_USDNoUSD ceiling per UTC day, persisted5.00
MAX_COST_PER_CALLNoUSD ceiling per tool invocation0.10
OPENROUTER_API_KEYNoRequired for OpenAI / Gemini / Claude via OpenRouter
PERPLEXITY_API_KEYNoRequired for Perplexity models in check_llm_mention
LLM_MAX_OUTPUT_TOKENSNoHard cap on output tokens per LLM call1024
AI_VISIBILITY_SPEND_FILENoOverride spend ledger location~/.cache/ai-visibility-mcp/spend.json

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_ai_bot_accessA

Check whether AI bots can read this site.

Fetches /robots.txt and the root URL. Reports per-bot allow/disallow plus Cloudflare AI-bot-default warning signals.

audit_ai_visibilityA

Composite AI-visibility audit for a domain.

Combines check_ai_bot_access with homepage scrape: meta robots tags (incl. noai/noimageai), JSON-LD structured data, sitemap.xml, llms.txt. Produces a 0-100 score with explainable reasons.

check_llm_mentionA

Check whether brand surfaces in LLM answers to query.

Fans out the same query to multiple LLMs (Perplexity sonar, OpenAI gpt-4o-mini, Gemini 2.0 Flash by default) and reports per-model mention + citations. Cost-capped via MAX_COST_PER_CALL env var.

compare_competitorsA

Side-by-side AI-visibility audit: your_domain vs competitors.

Runs audit_ai_visibility in parallel for all domains and returns a ranked comparison (score, blocked bots, JSON-LD presence, llms.txt, sitemap size, Cloudflare challenge state).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: audit_ai_visibility performs a comprehensive composite audit, check_ai_bot_access focuses solely on robots.txt and bot access, check_llm_mention checks LLM responses for brand mentions, and compare_competitors runs audits across multiple domains. No two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: audit_ai_visibility, check_ai_bot_access, check_llm_mention, compare_competitors. The verbs (audit, check, compare) clearly indicate the action, and nouns describe the target.

Tool Count5/5

With 4 tools, the server covers its core domain—AI visibility auditing—without being excessive or insufficient. Each tool contributes a distinct operation: detailed audit, specific check, LLM search, and competitive comparison.

Completeness5/5

The tool surface is complete for the domain: it includes a comprehensive audit (robots, sitemap, JSON-LD, llms.txt), a specific robots.txt check, LLM mention analysis, and competitor comparison. No obvious missing operations like per-resource checks are needed, as they are covered by the composite audit.

Maintenance

ActivityInactive
ResponsivenessNo issues