StudioMeyer GEO MCP

StudioMeyer GEO exposes AI visibility research and crawler-readiness checks through a hosted MCP endpoint with tool-specific access requirements.

Remote serverstreamable-http

What is the StudioMeyer GEO MCP Server?

StudioMeyer GEO exposes AI visibility research and crawler-readiness checks through a hosted MCP endpoint with tool-specific access requirements.

Separate site checks from model sampling

The service includes robots, llms.txt and JSON-LD inspection alongside brand-visibility workflows that query model platforms. Several structural checks work without an LLM API key; live model checks need the corresponding access. A generated visibility score is a product measurement, not a guaranteed search position.

Use the hosted MCP route

The registry manifest documents Streamable HTTP. The README also supplies an mcp-remote bridge for local-process clients. Background check tools return a job identifier that must be polled for the final result. Account tiers and provider keys affect which operations are available.

Inspect the inputs behind recommendations

Start with the site's robots file, canonical pages, sitemap and structured data, then compare any reported issue with the actual page. For model visibility, retain the prompts and sampled responses and repeat the measurement when assessing a change. A single stochastic response should not be treated as complete market coverage. Review a suggested schema or content change before publishing it.

Project documentation

Repository and setup guide

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
geo_checkFull GEO check pipeline across 8 LLM platforms. Optional samples (N>1) runs each prompt N times and collapses the draws into one statistically-defensible result + a reproducibility summary (a single LLM query is one stoc
geo_discovery_stackllms.txt + agents.json + robots.txt + JSON-LD + sitemap + FAQ schema
geo_calculate_scorePure scoring function from raw data
geo_platformsLLM platform readiness check (8 platforms)
geo_preview_promptsPreview prompts without making API calls
geo_analyze_responseParse a single LLM response for brand mentions. Optional hallucination guard (verifyUrls, extractClaims, claimsReference) cross-checks LLM-cited URLs against the real web and tags numeric claims as verified / refuted / u
geo_recommendationsGenerate actionable recommendations from scores
geo_robots_auditDeep robots.txt analysis with 14-AI-bot matrix
geo_llms_txt_validateValidate llms.txt against llmstxt.org spec with link checking
geo_json_ld_auditExtract and audit JSON-LD structured data
geo_entity_consistencyScan for brand name variants. Masks emails, URLs, and bare brand-domain refs before matching, so ahoi@example.com is not counted as a variant. Fragmented entities = 2.8x fewer AI citations.
geo_content_freshnessSitemap-first freshness audit. Reads robots.txt, walks sitemap_index, scores top-N URLs by lastmod + Last-Modified + og:modified_time + schema dateModified. Hardcoded i18n paths only as last-resort fallback.
geo_simulateEstimate GEO score without API keys (~30s, free)
geo_schema_generatorGenerate missing JSON-LD blocks ready to paste
geo_content_auditAudit content according to its page type.
geo_check_startStart a background visibility check.
geo_check_resultRetrieve a background check result.

How to install the StudioMeyer GEO MCP Server

{
  "mcpServers": {
    "studiomeyer-geo": {
      "url": "https://geo.studiomeyer.io/mcp"
    }
  }
}

Configuration

An HTTP MCP client, with provider keys or service access for the selected live-check and account-tier workflows.

Example prompts to try

  • “Use Studiomeyer Geo to geo check.”
  • “Use Studiomeyer Geo to geo discovery stack.”
  • “Use Studiomeyer Geo to geo calculate score.”

Frequently asked questions

No. The README distinguishes structural site checks from live model-query workflows that need provider access.