Geo MCP Server

AI search optimization analysis with actionable findings and gap analysis

Local serverstdio

What is the Geo MCP server?

If you already use Geo, the geo mcp server is the piece that lets your assistant work with it directly. AI search optimization analysis with actionable findings and gap analysis.

What the server does

Content analysis for AI search visibility. Measures what actually matters for getting cited by ChatGPT, Claude, Perplexity, and Google AI Overviews.

  • Claim Density — - Extractable facts per 100 words
  • Information Density — - Word count vs predicted AI coverage
  • Answer Frontloading — - How quickly key information appears
  • Semantic Triples — - Structured (subject, predicate, object) relationships
  • Entity Recognition — - Named entities AI can reference
  • Sentence Structure — - Optimal length for AI parsing

Installation

The server ships on npm as @houtini/geo-analyzer, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Requirements — The Requirements tool exposed by this server
  • Recommendations — Prioritised suggestions with: - Specific locations in content - Before/after examples - Rationale based on research
  • analyze_url — The analyze_url tool exposed by this server
  • analyze_text — The analyze_text tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: ANTHROPIC_API_KEY, GEO_WORKER_URL, JINA_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Geo's toolset — Requirements, Recommendations, analyze_url and 1 more — is a fair guide to whether it matches your workflow. It is maintained by houtini-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Geo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
RequirementsThe Requirements tool exposed by this server.
RecommendationsPrioritised suggestions with: - Specific locations in content - Before/after examples - Rationale based on research
analyze_urlThe analyze_url tool exposed by this server.
analyze_textThe analyze_text tool exposed by this server.

How to install the Geo MCP server

{
  "mcpServers": {
    "geo-analyzer": {
      "command": "npx",
      "args": ["-y", "@houtini/geo-analyzer@latest"],
      "env": {
        "ANTHROPIC_API_KEY": "sk-ant-..."
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ANTHROPIC_API_KEYCredential the server authenticates with.Yes
GEO_WORKER_URLEndpoint or connection string the server talks to.Yes
JINA_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Geo to Requirements.
  • Use Geo to Recommendations.
  • Use Geo to analyze url.

Frequently asked questions

It connects Geo to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Requirements, Recommendations, analyze_url, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Geo directly.