Distance, area, union, intersect and point-in-polygon all run without an API call, so a chain like isochrone then union then a point-in-polygon test touches the network at the first step only. What takes reading is the ordering: several tools point at each other, and the map renderer expects the reference another tool returned.
Mapbox's own server, split between calls to the search, routing and imagery APIs and a set of geometry operations that run locally without any API call. Run it yourself, or point a client at Mapbox's hosted endpoint.
- Search that distinguishes a name from a type: one tool for brands, addresses and towns, another for generic categories, and place details covering photos, opening hours, ratings, phone numbers and website URLs
- A grounding call that answers what is near a coordinate in one pass, covering reverse geocoding, place search and travel-time reachability together
- Routing in four shapes: turn-by-turn directions, a travel-time matrix between many points, an optimal visiting order for 2 to 12 coordinates, and isochrone contours for what is reachable within a time
- A noisy GPS trace of 2 to 100 points snapped onto roads, bike paths or walkways, returned with confidence scores
- Geometry that runs locally: distance, bearing, midpoint, destination, length, area, bounding box, centroid, convex hull, buffer, simplify, union, intersect, difference, point-in-polygon tests, nearest point, and nearest point on a line
- Two ways to show the result: a live Mapbox GL JS map with markers, layers and a legend rendered inside the chat, and a static image for clients that cannot render one
- Hand-composed GeoJSON rendered on that map directly — your own polygons and routes, with no other Mapbox call involved
- Disambiguation asked of the user when a search or a route is ambiguous, with a graceful fallback where the client cannot ask
A Mapbox access token in MAPBOX_ACCESS_TOKEN — a free account's default public token is enough to start — and Node.js, or Docker, or neither if you use the hosted endpoint at https://mcp.mapbox.com/mcp. The geometry tools work on the coordinates you pass them and need no network at all. Clients that do not support MCP resources need CLIENT_NEEDS_RESOURCE_FALLBACK=true to get the same content through tool calls; most clients do support them and should leave it unset. MIT licensed.
One command plus a key — npx -y @mapbox/mcp-server, then supply credentials