geo_analyze — Mapsource Geospatial API MCP Tool
geo_analyze
(geo analyze) is one of 13 tools on the
Mapsource Geospatial API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call geo_analyze from your client
- Claude Code Mapsource Geospatial API geo_analyze run in your project directory
- Claude Desktop Mapsource Geospatial API geo_analyze ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mapsource Geospatial API geo_analyze ~/.cursor/mcp.json
- VS Code Mapsource Geospatial API geo_analyze .vscode/mcp.json
- Zed Mapsource Geospatial API geo_analyze ~/.config/zed/settings.json
- Windsurf Mapsource Geospatial API geo_analyze ~/.codeium/windsurf/mcp_config.json
- Cline Mapsource Geospatial API geo_analyze ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mapsource Geospatial API geo_analyze ~/.gemini/settings.json
- Grok Mapsource Geospatial API geo_analyze .mcp.json (in your project root)
- ChatGPT Mapsource Geospatial API geo_analyze Settings → Connectors → Advanced → Developer mode
- Claude.ai Mapsource Geospatial API geo_analyze Settings → Connectors → Add custom connector
- LangChain Mapsource Geospatial API geo_analyze pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mapsource https://mapsource.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.