Skip to content
← Directory

mcp · Global

mapbox-mcp

AI-Powered 2D/3D Map Control via Model Context Protocol for Mapbox GL JS

Claim this listing

Represent mapbox-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified
map control capabilities: camera, layers, markers, sources, 3D terrain
Formats docs-verified
MCP stdio · WebSocket JSON-RPC 2.0 (runtime to browser bridge)
Access docs-verified
Mapbox access token required (API key). Open source, MIT licence.

Useful for

Use cases llm-inferred
Web map viewer of flood-zone and site-boundary layers in a Mapbox GL JS app, driven by an AI agent · Drawing proposed drainage routes or SuDS locations as GeoJSON over 3D terrain for client presentations · Flying the map camera to catchment or site extents for stakeholder consultation maps
Audience llm-inferred
GIS analysts · planners · civils and drainage engineers building web map viewers

Limitations

Constraints llm-inferred
Map control only: no datasets (rainfall, river levels, DEM, flood extents) are offered · Needs a Mapbox GL JS map open in a browser with the bridge connected to ws://localhost:9200 · Only 5 default toolsets (about 30 tools) are active; draw, style and 3d must be enabled with enable_toolset · ENTRY lists only list_toolsets and enable_toolset, while DOCS describe 40+ tools · ENTRY auth cites env var YOUR_TOKEN, but DOCS show the token entered on the browser page

Example tool calls docs-verified

Fly the camera to the Eiffel Tower, the example from DOCS. Argument names assumed from Mapbox GL JS flyTo options; not documented in DOCS.

{
  "tool": "flyTo",
  "arguments": {
    "center": [
      2.2945,
      48.8584
    ],
    "zoom": 16
  }
}
Licence
MIT
Authentication
API key via env: YOUR_TOKEN (auto-extracted from README)
GitHub stars
4
Last commit
26/03/2026
Last successful page check
14/10/2026
Page health
healthy
Package
npm:mapbox-mcp-runtime
Verification
Not independently verified

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Provenance & evidence

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 15/10/2026 · research sweep: github-search