GeoRanker

GeoRanker MCP Server (AI‑Agent Optimized)

Anagent-friendlyModel Context Protocol (MCP) server for theGeoRanker High‑Volume API.

- Compact, structured tool outputs(no LLM “summaries” — deterministic previews + truncation)
- Large payloads via resources(raw JSON available throughgeoranker://…resources instead of bloating tool outputs)
- Multi‑transport support

- stdio(Claude Desktop, local MCP clients)
- Streamable HTTP(recommended for Cursor, OpenAI Remote MCP, hosted use)
- Deprecated HTTP+SSE(optional compatibility for older clients)

- Deterministically shaped(top-N previews, key fields extracted)
- Truncated safely(string/array/object caps)
- Structured(JSON output +structuredContent)
- Raw data accessible on-demandvia resources like:

- georanker://serp/{id}
- georanker://keywords/{id}
- georanker://regions

- Claude Desktop (stdio)
- Cursor (Streamable HTTP)
- OpenAI Remote MCP (Streamable HTTPor HTTP+SSE)
- LangChain / any Node app (via MCP client OR OpenAPI endpoints)

npm i -g georanker-mcp # or run without install: npx georanker-mcp --help

GEORANKER_API_KEY=your_key_here GEORANKER_API_BASE_URL=https://api.highvolume.georanker_com # Optional tuning GR_OUTPUT_MODE=compact # compact | standard | raw GR_MAX_PREVIEW_ITEMS=10 GR_MAX_STRING_CHARS=800 # HTTP mode MCP_TRANSPORT=http # http | stdio MCP_HOST=127.0.0.1 MCP_PORT=3333 MCP_PATH=/mcp MCP_ENABLE_DEPRECATED_SSE=true # enables /sse + /messages MCP_AUTH_TOKEN= # optional bearer token MCP_PUBLIC_URL= # optional public https url used in server card/openapi

georanker-mcp --apikey YOUR_KEY georanker-mcp --transport http --host 127.0.0.1 --port 3333 --path /mcp georanker-mcp --transport http --auth-token mysecret georanker-mcp --legacy # expose deprecated snake_case tool names

2) HTTP mode (recommended for Cursor / hosted)

GEORANKER_API_KEY=... georanker-mcp --transport http --port 3333

- MCP Streamable HTTP:http://127.0.0.1:3333/mcp
- Deprecated SSE:http://127.0.0.1:3333/sse(andPOST /messages)
- OpenAPI:http://127.0.0.1:3333/openapi.json
- Server Card:http://127.0.0.1:3333/.well-known/mcp/server-card.json

{ "mcpServers": { "georanker": { "command": "npx", "args": ["-y", "georanker-mcp"], "env": { "GEORANKER_API_KEY": "YOUR_KEY" } } } }

- Run the server in HTTP mode (--transport http)
- In Cursor, add an MCP server with URL:

- http://127.0.0.1:3333/mcp(local)
- or your deployed HTTPS URL for hosted usage

Deploy the HTTP server to a public HTTPS URL, then configure aremote MCP toolpointing to:

- https://your-host/mcp(Streamable HTTP)
- orhttps://your-host/sse(deprecated HTTP+SSE)

Option A: use an MCP client to connect to the MCP endpoint. Option B: call the OpenAPI endpoints under/api/v1/*.

The recommended tool names are namespaced:

SetGR_ENABLE_LEGACY_TOOL_NAMES=trueor run with--legacyto also expose the old snake_case tools.

All tools return compact JSON shaped like:

{ "ok": true, "action": "georanker_serp.get", "generated_at": "2026-02-19T12:00:00.000Z", "request": { "id": "..." }, "data": { "...compact preview..." }, "links": { "raw_resource": "georanker://serp/..." } }

If a tool fails, it returnsok:falseand the MCP tool result will includeisError:true.

URL publish (recommended for hosted servers):

- Make sure Streamable HTTP is available at/mcp
- Ensure server card exists at/.well-known/mcp/server-card.json

Then publish from the Smithery UI or via CLI:

smithery mcp publish "https://your-host/mcp" -n @lucas111112/georanker-mcp

smithery mcp publish --name @lucas111112/georanker-mcp --transport stdio

Search global news using natural language. Webz.io News Search API returns the most relevant articles and content, with filters for source, country, language, date, sentiment, and category.

SEO + GEO MCP server: live Google Search Console & GA4 data, keyword/page analysis and SEO tasks from chat.

All-in-One SEO & Web Intelligence Toolkit API from FetchSERP.

Access to your site's SEO data — crawl results, Search Console and Analytics, so your assistant can tell you what's broken, what's ranking, and what to fix next.

AI-powered keyword research, SERP analysis, backlink checking, and content optimization for SEO.

An MCP server for accessing Google Search Console data, including site performance and indexing status.

Read-only MCP server for Google Search Console: search analytics, URL inspection, and sitemaps

Google Search Console MCP for Claude Code

Google Search Console MCP for Claude Code & Cursor with built-in SEO intelligence: traffic-drop diagnosis, quick wins, content decay, cannibalization, ranking alerts. Read-only by default, with anti-hallucination provenance metadata on every response.

A Model Context Protocol (MCP) server providing access to Google Search Console & Google analytics

Interact with the Haloscan SEO API for search engine optimization tasks.