Bbox Mcp Server
Equip your agent with geospatial tools—bounding boxes, H3 grids, coord conversion, OSM Overpass search, and map verification links—for location-aware features.
Overview
bbox MCP is a build-phase MCP server that gives agents geospatial queries, H3 grids, OSM Overpass search, coordinate conversion, and map verification links via npm stdio.
What is this MCP server?
- Spatial queries, coordinate conversion, and H3 indexing with MAX_H3_CELLS safety cap (default 50000)
- OpenStreetMap search via configurable OVERPASS_API_URL with public instance rotation
- Optional MAPBOX_ACCESS_TOKEN for natural-language place lookup (e.g. San Francisco)
- Map verification links for human review of agent-produced geometries
- npm bbox-mcp-server v1.2.6 stdio; website vibhorsingh.com/boundingbox/
- Package version 1.2.6; identifier bbox-mcp-server on npm
- Default MAX_H3_CELLS safety cap 50000 for H3 grid generation
- Three documented environment variables: MAPBOX_ACCESS_TOKEN, OVERPASS_API_URL, MAX_H3_CELLS
Community signal: 3 GitHub stars.
What problem does it solve?
Building even simple geo features forces indie developers to stitch Mapbox, Overpass, and projection math by hand for every agent-assisted task.
Who is it for?
Solo builders adding maps, geo filters, or fleet tiles to an agent-driven codebase who want one MCP geospatial surface.
Skip if: Projects with no location dimension, or teams that already standardised on a single proprietary GIS suite with its own MCP.
What do I get? / Deliverables
After MCP registration, your agent can run bounded spatial operations and return verification links without custom geospatial scripts in the repo.
- Agent-computed bounding regions, H3 cell sets, and converted coordinates
- OSM search results and human-readable map verification URLs
Recommended MCP Servers
Journey fit
Location logic is implemented during build when you wire maps, geo filters, and external spatial APIs into the product or agent workflows. Integrations captures MCP bridges to Mapbox, Overpass, and H3 utilities rather than frontend-only map UI work.
How it compares
Geospatial developer MCP toolkit, not a hosted map tile CDN or mobile SDK.
Common Questions / FAQ
Who is bbox MCP for?
Developers and indie founders using Claude Code or Cursor to build location-aware apps who need H3, OSM, and coordinate tools through MCP.
When should I use bbox MCP?
Use it during build integrations while prototyping geo search, service areas, or agent-verified map bounds before you ship perf-tested backends.
How do I add bbox MCP to my agent?
npm install/run bbox-mcp-server 1.2.6 with stdio in your MCP config, set MAPBOX_ACCESS_TOKEN if you need NL geocoding, optionally OVERPASS_API_URL and MAX_H3_CELLS, then restart the host.