Gods Eye Geospatial Mcp
Give your agent geospatial lookups and map-adjacent data so location features ship without hand-rolled API glue in every prompt.
Overview
gods-eye-geospatial-mcp is a MCP server for the Build phase that exposes geospatial and location data capabilities to agents over stdio.
What is this MCP server?
- stdio MCP server gods-eye-geospatial-mcp at manifest version 1.2.3
- PyPI distribution with identifier gods-eye-geospatial-mcp
- MEOK AI Labs geospatial tooling under CSOAI-ORG on GitHub
- Suited for agents building dashboards, check-ins, or geo filters
- Model Context Protocol schema 2025-12-11 compliant manifest
- PyPI package gods-eye-geospatial-mcp with stdio transport
- Single package entry in MCP server.json
What problem does it solve?
Building geo features forces repeated context-switching between map APIs, docs, and the agent without structured spatial tools.
Who is it for?
Indie builders shipping location-aware SaaS, mobile, or API products who want agent help wiring geospatial integrations.
Skip if: Projects with no map or location requirements, or teams that need enterprise GIS desktop workflows only.
What do I get? / Deliverables
After registration, your agent can call geospatial MCP tools while you design backends, APIs, or map UX.
- Agent-callable geospatial MCP tools in local dev
- Faster iteration on location-backed features during build
- Documented stdio server entry for your project MCP bundle
Recommended MCP Servers
Journey fit
Map and geospatial features usually land during product build when you wire external location APIs into the app or agent workflow. Geospatial MCP is an integration layer between your agent and spatial datasets or services, not a launch-only SEO tool.
How it compares
Geospatial MCP integration, not a map design skill or a hosted mapping SaaS by itself.
Common Questions / FAQ
Who is gods-eye-geospatial-mcp for?
Solo builders and small teams using MCP agents to implement maps, regions, or location analytics in their product.
When should I use gods-eye-geospatial-mcp?
Use it during Build when integrating geospatial APIs, validating queries, or scaffolding location features with an agent.
How do I add gods-eye-geospatial-mcp to my agent?
Install the PyPI package gods-eye-geospatial-mcp, add a stdio MCP server block in your agent config, and reload.