The geospatial toolkit for AI agents — query, convert, and verify spatial data with zero config. 6 tools for bounding boxes, coordinate projection
The geospatial toolkit for AI agents — query, convert, and verify spatial data with zero config. 6 tools for bounding boxes, coordinate projection, H3 indexing, OpenStreetMap queries, and shareable map verification links. The bbox mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.
The geospatial toolkit for AI agents. 6 tools, zero config — give any LLM the ability to find, query, convert, and aggregate spatial data using open data. No API keys or signups required to start.
Everything the assistant can do here goes through one of these:
get_bounds — Convert and project a bbox across formats and coordinate systemsget_h3_indices — Generate H3 hex cell indices covering a bboxgenerate_share_url — Create a shareable map link for a bboxsearch_overpass — Query OpenStreetMap via Overpass QL within a bbox or radiuslist_osm_tags — Look up correct OSM tags for a categoryaggregate_overpass_h3 — Run an Overpass query and bin results into H3 hexagonsLogging — Structured JSON logs go to stderr (stdout is reserved for MCP protocol). Each entry includes timestamp, level, and contextOpenStreetMap — The OpenStreetMap tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at bbox-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: MAPBOX_ACCESS_TOKEN, OVERPASS_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Bbox's toolset — get_bounds, get_h3_indices, generate_share_url and 5 more — is a fair guide to whether it matches your workflow. It is maintained by iamvibhorsingh; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_bounds | Convert and project a bbox across formats and coordinate systems |
| get_h3_indices | Generate H3 hex cell indices covering a bbox |
| generate_share_url | Create a shareable map link for a bbox |
| search_overpass | Query OpenStreetMap via Overpass QL within a bbox or radius |
| list_osm_tags | Look up correct OSM tags for a category |
| aggregate_overpass_h3 | Run an Overpass query and bin results into H3 hexagons |
| Logging | Structured JSON logs go to **stderr** (stdout is reserved for MCP protocol). Each entry includes timestamp, level, and context. |
| OpenStreetMap | The OpenStreetMap tool exposed by this server. |
{
"mcpServers": {
"bbox": {
"command": "npx",
"args": ["-y", "bbox-mcp-server"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MAPBOX_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| OVERPASS_API_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.