Mapsi Mcp
Let your coding agent geocode addresses, plan routes, draw isochrones, and query H3 grids without hand-rolling OpenStreetMap APIs.
Overview
mapsi-mcp is a MCP server for the Build phase that exposes 17+ OpenStreetMap geospatial tools—geocoding, routing, isochrone, H3, and elevation—to your agent via Mapsi.
What is this MCP server?
- 17+ geospatial MCP tools: geocoding, routing, isochrone, H3, elevation, and 13 more on OpenStreetMap data
- Stdio npm package mapsi-mcp with MAPSI_API_KEY from mapsi.dev
- Suited for location-aware SaaS, logistics prototypes, and field-service UIs
- Agent-callable tools instead of copying REST docs into every session
- OpenStreetMap-backed queries for builders avoiding proprietary map SDK lock-in early
- 17+ geospatial tools advertised (geocoding, routing, isochrone, H3, elevation, and 13 more)
- Registry version 1.0.0
- Transport: stdio via npm package mapsi-mcp
What problem does it solve?
Agents cannot reliably plan map features when every geocode and route request means you paste API docs and curl examples by hand.
Who is it for?
Indie builders adding OpenStreetMap-based location features to a SaaS, API, or mobile app through an agent-assisted integration pass.
Skip if: Teams that only need a static embedded map with no agent-driven geospatial queries, or builders without a Mapsi API key.
What do I get? / Deliverables
After you add mapsi-mcp and a MAPSI_API_KEY, your agent can call structured geospatial tools while you implement location logic in code.
- Registered stdio MCP server in your agent config
- Agent-accessible geocoding, routing, and related OSM tool calls
- Faster iteration on location-feature code against live Mapsi responses
Recommended MCP Servers
Journey fit
Geospatial features land when you wire external services into the product, which is the integrations shelf on the build phase. Mapsi exposes many map and location tools as MCP calls, matching how solo builders add routing, elevation, and search to apps.
How it compares
Geospatial MCP tool pack backed by Mapsi, not a general-purpose code-review or planning skill.
Common Questions / FAQ
Who is mapsi-mcp for?
Solo developers and small teams who want their AI coding agent to run geocoding, routing, isochrones, and related OSM workflows through MCP while building map-related product features.
When should I use mapsi-mcp?
Use it during build when you are integrating location services—addresses, routes, catchment areas, or elevation—into your app and want the agent to call Mapsi instead of guessing REST payloads.
How do I add mapsi-mcp to my agent?
Install the npm package mapsi-mcp, set the secret environment variable MAPSI_API_KEY from mapsi.dev, and register the stdio MCP server in Claude Code, Cursor, or another MCP-compatible client.