geoseo-mcp

What this does

geoseo-mcp exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GEOSEO_OPENAI_API_KEY
GEOSEO_ANTHROPIC_API_KEY
GEOSEO_GEMINI_API_KEY
GEOSEO_PERPLEXITY_API_KEY
GEOSEO_XAI_API_KEY
GEOSEO_BRAVE_API_KEY
GEOSEO_SERPAPI_API_KEY
GEOSEO_BING_WEBMASTER_API_KEY
GEOSEO_YANDEX_OAUTH_TOKEN
GEOSEO_INDEXNOW_KEY
GEOSEO_GOOGLE_CLIENT_SECRET
GEOSEO_TOOLSETS

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install geoseo-mcp?

Run the Claude Code command in the install section to add geoseo-mcp to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with geoseo-mcp?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to geoseo-mcp as well.

Does geoseo-mcp need an API key?

Yes. Before it can run, set these environment variables: GEOSEO_OPENAI_API_KEY, GEOSEO_ANTHROPIC_API_KEY, GEOSEO_GEMINI_API_KEY, GEOSEO_PERPLEXITY_API_KEY, GEOSEO_XAI_API_KEY, GEOSEO_BRAVE_API_KEY, GEOSEO_SERPAPI_API_KEY, GEOSEO_BING_WEBMASTER_API_KEY, GEOSEO_YANDEX_OAUTH_TOKEN, GEOSEO_INDEXNOW_KEY, GEOSEO_GOOGLE_CLIENT_SECRET, GEOSEO_TOOLSETS. They go in the env block of your MCP config.