CiteContext MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CITECONTEXT_API_KEY | No | Workspace API key for authenticated client tools & automated PR creation. Optional for public audit & generation tools. | |
| CITECONTEXT_API_URL | No | CiteContext backend gateway URL. | https://citecontext.com/api/mcp/run |
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 |
|---|---|
| geo_audit_domainB | Run an 8-category Generative Engine Optimization (GEO) audit on any website domain. Evaluates robots.txt AI bot directives, llms.txt availability, JSON-LD Schema veracity, and Princeton KDD citability factors. |
| generate_llms_txtB | Generate a compliant machine-readable llms.txt and llms-full.txt specification for AI assistants and LLM crawlers from a sitemap or website root. |
| generate_robots_txtA | Generate an optimized robots.txt file that allows real-time AI citation search bots (Claude-SearchBot, OAI-SearchBot, Google-Extended) while controlling offline model training scrapers. |
| check_ai_bot_accessA | Check if major AI search engines (Claude, ChatGPT Search, Gemini, Google AI Overviews) are permitted or blocked by a website's live robots.txt. |
| generate_schema_jsonB | Generate validated Schema.org JSON-LD structured data for SoftwareApplication or Organization. Pass same_as only with VERIFIED profile URLs (Wikidata Q-item, LinkedIn, GitHub) — links are never invented. |
| get_ai_search_visibilityB | Measure brand visibility, mention frequency, and sentiment across generative AI engines (Claude, ChatGPT Search, Gemini) for target buyer queries. |
| get_ai_search_cited_sourcesB | Identify which external sources, reference URLs, and authority domains AI models cite when answering commercial queries in your category. |
| track_competitor_generative_gapB | Conduct a head-to-head GEO comparison between your brand and a competitor across generative recommendation share, entity grounding, and crawler permissions. |
| analyze_gsc_ai_overviewsC | Analyze Google Search Console queries to identify Google AI Overview (AIO) trigger probability and prevent zero-click answer displacement. |
| client_snapshotA | Pull the stored AI-visibility analytics snapshot for one CiteContext client workspace: visibility history, per-engine breakdown, per-prompt trends, and the current action plan. Reads only recorded sweep data — nothing is estimated. |
| client_promptsA | Manage a client workspace's prompt library: list saved prompts with per-prompt visibility trends, add a new sweep prompt, or pause/resume one. |
| discover_promptsC | Discover high-intent buyer prompts across 4 strategic pillars (commercial evaluation, head-to-head comparison, technical architecture, pricing ROI) with Princeton KDD lift tactics. |
| analyze_agent_logsA | Parse raw web server or edge access logs to identify incoming AI crawler traffic (GPTBot, ClaudeBot, PerplexityBot, Google-Extended), status codes, and blocked paths. |
| audit_page_geoB | Run a deep page-level Generative Engine Optimization (GEO) audit on a single URL. Analyzes Princeton KDD factual density, H1/H2 chunking, Schema JSON-LD, and context window token efficiency. |
| deploy_github_prA | Deploy verified GEO remediation files (AI crawler-unblocking robots.txt, /llms.txt, Schema.org JSON-LD) directly to a GitHub repository by opening an automated Pull Request with zero human intervention. |
| get_remediation_patchB | Get the exact zero-touch file patch (public/robots.txt, public/llms.txt, Schema JSON-LD) for a website. Enables AI coding agents like Claude Code, Cursor, Windsurf, or ChatGPT to write and deploy these files directly into the local workspace repository with zero manual copy-pasting. |
| searchB | Search the CiteContext public knowledge base (GEO playbook, AI citation research, llms.txt and schema guides). Required |
| fetchA | Fetch the full readable text of a CiteContext knowledge-base page by id/URL. Required |
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 18 tools
Most tools target clearly distinct actions and artifacts (generate robots vs llms.txt vs schema, domain audit vs page audit, get patch vs deploy PR). A few pairs like geo_audit_domain/audit_page_geo and the two generate_* file tools are close enough that an agent might momentarily hesitate, but descriptions clarify the boundary.
The majority follow a readable verb_noun snake_case pattern (generate_robots_txt, track_competitor_generative_gap, analyze_gsc_ai_overviews). However several outliers break the pattern: bare verbs (search, fetch) and noun-only names (client_snapshot, client_prompts) mix conventions.
18 tools is sizable but each maps to a distinct GEO/visibility workflow, so they largely earn their place. It sits near the upper end of comfortable but remains reasonable for a full-featured platform rather than feeling bloated.
The surface spans generation (robots, llms.txt, schema), auditing (domain, page, GSC, logs), visibility measurement, competitor comparison, and remediation/deploy — strong lifecycle coverage. Minor gaps exist, such as managing multiple workspaces or editing competitor/entity records beyond the read-focused snapshot tools.