All servers / Maps / Mapbox (official)
Mapbox (official)
Geocoding, routing and maps.
Tested by ConnectATDScore 82 out of 100. Tested 2026-11-17 on package version 0.18.1. Package: @mapbox/mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 12 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (109.8 seconds including download)
- Tools offered: 32
- Last published: 2026-11-17
- Weekly downloads (npm): 4,914
- License: MIT · Direct dependencies: 15
Notes
- The package runs install scripts, which execute code when you install it.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_public_tokens_tool1 of 1 parameter describedLists the Mapbox account's public (pk.) access tokens, for when you build a web page or app outside this chat that loads Mapbox GL JS or calls Mapbox APIs from the browser. Put the returned pk. token in the page: public tokens are made to ship in browser code, so a placeholder or asking the user to paste a token is not needed. To show a map in the chat, use render_map_tool instead; it needs no token. Pass site_url (where the page will run) to get a token restricted to that URL when the account has one. Returns each token's name, whether it is the default, its URL restrictions and scopes, a recommended token, and guidance: for a published site, use a URL-restricted token, and tell the user the default token can be reused by anyone who copies it. Secret tokens are never listed.
feedback_tool4 of 4 parameters describedSend the user's feedback about this app or agent to its developer, through the Mapbox Feedback API (Public Preview), so the developer can understand what users need and improve the product. Feedback can be about anything in the product: for example a place that has closed or has wrong details, a missing place, a closed road, a route with an illegal turn, a wrong travel time, or something about the app itself. It is filed under the Mapbox account that owns the access token, in the same feed as that account's Feedback Agent reports, and the developer reviews it in Feedback Explorer. It does not report the problem to Mapbox. Use it only when the user asks to send feedback, or agrees when you offer. Before calling it, show the user the exact feedback text, category and location you will send and get their go-ahead. Take the coordinates from an earlier search, place or directions result rather than guessing, and leave them out when the feedback is not about a place, such as most feedback about the app itself. Send one report per problem, and do not resend one that already succeeded. To avoid filing the same problem twice, the tool first checks the account's own reports from the last 30 days and does not send if one with the same category within 50 m is still awaiting review; it returns that report instead. Only set send_anyway when the user says the earlier report is about a different problem. Returns the item id and its status (received).
report_tool3 of 3 parameters describedSend feedback about the Mapbox MCP server to the Mapbox team that builds it: a bug, a tool that failed or gave a wrong or confusing result, a missing capability or a suggestion. It goes to Mapbox, not to the user's account, needs no special token scope, and cannot be read back or withdrawn afterward. It is for feedback about this server, not for reporting wrong map, place or routing data. Use it only when the user asks to send feedback, or agrees when you offer. Before calling it, show the user the exact text you will send and get their go-ahead. Leave out personal details the user did not ask to share. The server adds its own version and the client name. Send one report per problem, and do not resend one that already succeeded. Returns the report id.
ground_location_tool7 of 7 parameters describedAnswer questions about what is near a location, what neighborhood a coordinate is in, or what places are within walking/driving distance. Use this when given coordinates and asked about nearby places, neighborhood context, local discovery, or area summaries. It already includes reverse geocoding, so a separate reverse_geocode_tool call is not needed for the same coordinate. Pass the place category (e.g. "restaurant", "coffee", "park") as the query parameter to get nearby POIs in the same call. Returns place name, nearby POIs matching the query, and travel-time reachability — all sourced from live Mapbox data with citations.
points_within_polygon_tool2 of 2 parameters describedTest one or more geographic points against a polygon, returning only those inside. Handles a single point or a batch of points in one call. Useful for delivery zone validation, fleet geofencing, and customer segmentation. Works offline without API calls.
union_tool1 of 1 parameter describedMerge two or more polygons into a single unified geometry. Useful for combining service areas, delivery zones, isochrones, or coverage regions. Returns a Polygon or MultiPolygon if the inputs do not overlap. Works offline without API calls. INPUT SHAPE: pass `polygons` as an array of polygons. Each polygon is an array of rings; each ring is an array of [lng, lat] pairs. When chaining with isochrone_tool, extract `feature.geometry.coordinates` from each isochrone Feature — that is already a valid Polygon value. Skip features whose `geometry.type === "MultiPolygon"` (pass each inner Polygon separately) or whose `geometry.type === "LineString"` (set isochrone_tool `polygons=true` to get Polygon output instead).
nearest_point_tool3 of 3 parameters describedFind the nearest point in a collection to a given target point. More efficient than calling distance_tool for each candidate and sorting. Useful for finding the closest store, stop, or landmark to a location. Works offline without API calls.
intersect_tool2 of 2 parameters describedFind the intersection geometry of two polygons — the area they share in common. Useful for coverage overlap analysis, finding shared service areas, or zone overlap. Returns null geometry if the polygons do not overlap. Works offline without API calls. INPUT SHAPE: `polygon1` and `polygon2` are each an array of rings; each ring is an array of [lng, lat] pairs. When chaining with isochrone_tool, extract `feature.geometry.coordinates` from each isochrone Feature (with `polygons=true`).
difference_tool2 of 2 parameters describedSubtract one polygon from another, returning the area in polygon1 that is not covered by polygon2. Useful for computing exclusion zones, finding uncovered service areas, or "what is in zone A but not zone B?". Returns null geometry if polygon2 fully covers polygon1. Works offline without API calls. INPUT SHAPE: `polygon1` and `polygon2` are each an array of rings; each ring is an array of [lng, lat] pairs. When chaining with isochrone_tool, extract `feature.geometry.coordinates` from each isochrone Feature (with `polygons=true`).
destination_tool4 of 4 parameters describedCalculate a destination point given a starting point, bearing, and distance using geodesic (great-circle) straight-line offset. Useful for "find a point 5km north of X", constructing search offsets, or computing waypoints. Bearing: 0=north, 90=east, 180/-180=south, -90=west. Note: this calculates a straight-line geographic offset, not road-network distance. Works offline without API calls.
length_tool2 of 2 parameters describedMeasure the total length of a line defined by a series of coordinates. Useful for measuring a drawn route, path, or boundary without a routing API call. Supports kilometers, miles, meters, and feet. Works offline without API calls.
nearest_point_on_line_tool3 of 3 parameters describedSnap a point to the nearest position on a line or route. Returns the closest point on the line and the distance to it. Useful for "which point on this route is closest to my location?" or map-matching without the API. Works offline without API calls.
convex_tool1 of 1 parameter describedCompute the convex hull of a set of points — the smallest convex polygon that contains all the points. Useful for bounding area analysis, estimating coverage area, or wrapping a set of locations. Works offline without API calls.
place_details_tool4 of 4 parameters describedRetrieve detailed information about a specific place using its Mapbox ID. Use after search_and_geocode_tool, category_search_tool, or reverse_geocode_tool to get additional details such as photos, opening hours, phone numbers, and website URLs. Requires the mapbox_id field from a previous search result. Primarily covers points of interest (businesses, addresses, buildings); mapbox_ids for neighborhoods, cities, or other administrative boundaries are also supported but return more limited data (name, address, coordinates — no photos, hours, or contact info). The primary POI lookup is Public Preview with a default quota of 1,000 requests/month; contact Mapbox if you need a higher volume.
simplify_tool3 of 3 parameters describedSimplify a LineString or Polygon by reducing the number of vertices while preserving the general shape. Uses the Douglas-Peucker algorithm. Useful for reducing file sizes and improving rendering performance. Works offline without API calls.
bbox_tool1 of 1 parameter describedCalculate the bounding box (extent) of any geometry. Returns the minimum and maximum longitude and latitude that encompass the geometry. Works offline without API calls.
centroid_tool1 of 1 parameter describedCalculate the geometric center (centroid) of a polygon or multipolygon. The centroid is the arithmetic mean position of all points in the shape. Works offline without API calls.
midpoint_tool2 of 2 parameters describedCalculate the geographic midpoint between two coordinates. Returns the point that is halfway between the two input points along the great circle path. Works offline without API calls.
bearing_tool2 of 2 parameters describedCalculate the bearing (compass direction) from one point to another. Returns bearing in degrees where 0° is North, 90° is East, 180° is South, and 270° is West. Works offline without API calls.
area_tool2 of 2 parameters describedCalculate the area of a polygon or multipolygon. Supports various units including square meters, kilometers, acres, and hectares. Works offline without API calls.
buffer_tool3 of 3 parameters describedCreate a buffer zone (polygon) around a point, line, or polygon at a specified distance. Useful for proximity analysis, service areas, or creating zones of influence. Works offline without API calls.
distance_tool3 of 3 parameters describedCalculate the distance between two geographic coordinates. Supports various units including kilometers, miles, meters, feet, and nautical miles. Uses the Haversine formula for accurate great-circle distance calculations. This tool works offline without requiring API calls.
category_search_tool8 of 8 parameters describedReturn all places that match a category (industry, amenity, or NAICS‑style code). Use when the user asks for a type of place, plural or generic terms like 'museums', 'coffee shops', 'electric‑vehicle chargers', or when the query includes is‑a phrases such as 'any', 'all', 'nearby'. Do not use when a unique name or brand is provided. Supports both JSON and text output formats.
directions_tool11 of 11 parameters describedFetches directions from Mapbox API based on provided coordinates and direction method. Returns a `mapboxRender.ref` in structuredContent regardless of the geometries value; if the user wants to see the route on a map, pass it to render_map_tool. Use geometries="none" (default) for compact text/data responses (distance, duration, turn-by-turn instructions, congestion). Use geometries="geojson" when you need the raw route coordinates in the response yourself, e.g. to draw the route in your own app. It defaults to a simplified geometry that keeps the route's shape when zoomed out but cuts corners up close; pass overview="full" for every vertex when your map lets people zoom in on the route. render_map_tool works either way. Only overview="full" on a very long trip can exceed the response size limit; then this tool returns a summary and a `mapbox://response/...` ref you can read with the MCP resources API.
isochrone_tool10 of 10 parameters describedComputes areas that are reachable within a specified amount of time from a location, and returns the reachable regions as contours of Polygons or LineStrings in GeoJSON format that you can display on a map. Common use cases: - Show a user how far they can travel in X minutes from their current location - Determine whether a destination is within a certain travel time threshold - Compare travel ranges for different modes of transportation'
map_matching_tool7 of 7 parameters describedSnap a recorded GPS trace to roads using Mapbox Map Matching API. Takes a dense, noisy coordinate sequence (2-100 points, recorded seconds or tens of meters apart) and returns a clean route aligned with actual roads, bike paths, or walkways. Useful for analyzing recorded trips, cleaning fleet tracking data, or processing fitness activity traces. Not for routing between a few places or addresses: points kilometers apart fail to match, so use directions_tool for that. Returns confidence scores, matched geometry, and optional traffic/speed annotations.
matrix_tool7 of 7 parameters describedCalculates travel times and distances between multiple points using Mapbox Matrix API. Put all the points in one call (up to 25, 10 for driving-traffic) rather than one call per pair: the API allows 60 requests per minute (30 for driving-traffic).
optimization_tool10 of 10 parameters describedFind the optimal (shortest by travel time) route through a set of 2-12 coordinates. Solves the Traveling Salesman Problem to determine the best visiting order. Supports options for starting point, ending point, and whether to return to start.
render_map_tool9 of 9 parameters describedDisplay a live, interactive Mapbox GL JS map. Use this when someone wants to see a location, route, or dataset on a map. Preferred usage: any other Mapbox tool returns a `mapboxRender.ref` URI in its structuredContent — pass that ref via `payload_refs: ["..."]`. You can pass multiple refs to merge several datasets (e.g. a search result + a route) onto one map. Inline `layers`/`markers`/`legend` fields are also supported for hand-composed payloads from raw GeoJSON. For a hand-composed POI marker (e.g. built from category_search_tool/search_and_geocode_tool/place_details_tool output), set `markers[].id` to the place's mapbox_id — this gets it the same auto-enriching results carousel (popularity score and photo) that a payload_refs-based search result gets automatically, with no extra tool calls. To restyle the base map itself (e.g. "make the water red", switch to night lighting, hide POI labels) pass `baseMapConfig`. To switch to satellite imagery, pass `baseStyle: "standard-satellite"` (defaults to "standard"). To show live traffic congestion on the roads in view, pass `showTraffic: true`. The map also has Satellite and Traffic buttons users can toggle themselves. Every call redraws the map from scratch: only the traffic and satellite settings carry over from the previous call. So to restyle an already-drawn map or toggle traffic without losing its content, re-pass the same `payload_refs`/`layers` alongside `baseMapConfig`/`baseStyle`/`showTraffic` rather than sending them alone. After rendering places, don't list them again in your reply: the map's cards already show each name, category, price level, distance and hours. Answer the question or add what the cards leave out (like the phone number or address) instead.
reverse_geocode_tool9 of 9 parameters describedConvert geographic coordinates (longitude, latitude) into a human-readable address or place name. Use only when you need an address/place name alone. If you also need nearby places, neighborhood context, or travel-time reachability, use ground_location_tool instead — it already includes reverse geocoding plus POI search and isochrone in one call. This tool cannot reverse geocode businesses, landmarks, or POIs. Supports JSON and text output formats.
static_map_image_tool6 of 6 parameters describedGenerates a static map image from Mapbox Static Images API. Supports center coordinates, zoom level (0-22), image size (up to 1280x1280), various Mapbox styles, and overlays (markers, paths, GeoJSON). Returns PNG for vector styles, JPEG for raster-only styles. Use only when the user explicitly asks for a static image file — to show a map, use render_map_tool instead, which renders an interactive map.
search_and_geocode_tool10 of 11 parameters describedSearch for POIs, brands, chains, geocode cities, towns, addresses. Do not use for generic place types such as 'museums', 'coffee shops', 'tacos', etc, because category_search_tool is better for that. Setting a proximity point is strongly encouraged for more local results. The underlying Search Box API is rolling out natural-language query understanding (e.g. 'quiet coffee shops with wifi near downtown'), so richer free-text phrasing in `q` can work well for category + place + attribute combinations — but as of this writing, big-box retail brand searches tied to a specific address (e.g. 'Costco near <address>', 'Walmart near <address>', 'Target near <address>') are unreliable and often return unrelated results; verify those results before relying on them.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.