geo-optimizer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_product_guideA | Get the complete guide for making a website visible in AI search engines (ChatGPT, Gemini, Grok, Claude). Call this FIRST when the user asks about AI search visibility, GEO optimization, why their site isn't cited by AI, or how to get mentioned in ChatGPT. Returns a step-by-step workflow explaining which tools to call and in what order. |
| analyze_geo_scoreA | Check the GEO (Generative Engine Optimization) score for any existing website. Returns an AI readiness score 0-100, grade A-F, and a breakdown of specific issues that reduce visibility in ChatGPT, Gemini, Grok, Claude, and other AI search engines. Use this for existing sites. For new or rebuilding sites, use make_site_geo_ready instead. After getting the score, call get_geo_fixes to get specific copy-paste fix instructions. |
| get_geo_fixesA | Get specific copy-paste fix instructions for a website's GEO (AI search) issues. Returns ready-to-use code for robots.txt, Organization Schema JSON-LD, FAQ Schema, and llms.txt — tailored to that site's current score and issues. Call this AFTER analyze_geo_score to get actionable fixes for an existing site. |
| make_site_geo_readyA | Generate all GEO (AI search optimization) assets for a website in one shot. Returns ready-to-use Organization Schema JSON-LD, FAQ Schema JSON-LD, llms.txt, and robots.txt snippet — so AI search engines like ChatGPT, Gemini, Grok, and Claude can find, understand, and cite the site. Use this when building or updating a website and the user wants AI search visibility. No API key required. |
| suggest_monitoring_configA | Generate a complete AI monitoring configuration for a business: target audience descriptions, monitoring location, and query suggestions. Use this when the user describes their business and wants to set up monitoring for the right audience and location. Returns ready-to-use configuration JSON and API instructions to apply it. AI agents can use this to auto-fill monitoring settings without the user having to manually describe their audience. |
| get_site_reportA | Get a client-ready report for a site: GEO score breakdown, and — if a Visibility Report share link (slug) is available — AI mention-rate results across engines (ChatGPT, Claude, Gemini, Grok). Use this when the user asks for 'a report on this site', 'how is this client doing', or wants something to hand to a client. Pass |
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 6 tools
Tool triggers and workflows are mostly distinct, with explicit cross-references (analyze then get_geo_fixes; guide first). However, get_geo_fixes and make_site_geo_ready produce overlapping artifacts (schema, llms.txt, robots.txt) and could be confused for existing vs. rebuilding sites, and analyze_geo_score overlaps with get_site_report on score reporting.
All tools use consistent snake_case with a verb-first pattern (analyze_, get_, make_, suggest_), making the set predictable and readable.
Six tools form a well-scoped set for a GEO optimization assistant; each tool covers a distinct phase (guide, audit, fixes, asset generation, monitoring config, reporting) without redundant entries.
The surface covers audit, remediation guidance, asset generation, monitoring suggestions, and reporting. Minor gaps remain: no tool to apply or validate generated assets, and no direct management of monitoring configs after suggestion.