Mapbox integration for MCP servers
Mapbox integration for MCP servers. Exposed over MCP by the mapbox mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
mapbox_matrix_by_places - Calculate travel time and distance matrices between places using their names - Inputs: - places (string[]): Array of place names (2-25 places) - profile (optional): "driving", "walking", "cycling" - annotations (optional): "duration", "distance", "duration,distance" - language (optional): Two-letter language code - sources (optional): Indices of source places - destinations (optional): Indices of destination places - Returns: - Geocoding results for each place - Matrix of durations and/or distances - Any errors that occurred during processingEverything the assistant can do here goes through one of these:
Inputs — - coordinates ({latitude: number, longitude: number}[])Returns — route details with steps, distance, durationPrerequisites — The Prerequisites tool exposed by this serverStructure — In mapbox-mcp-server, we use the following structure to manage the server's handlers:You will need one environment variable: MAPBOX_ACCESS_TOKEN. 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.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mapbox's toolset — Inputs, Returns, Prerequisites and 1 more — is a fair guide to whether it matches your workflow. It is maintained by AidenYangX; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Inputs | - coordinates ({latitude: number, longitude: number}[]) |
| Returns | route details with steps, distance, duration |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Structure | In mapbox-mcp-server, we use the following structure to manage the server's handlers: |
{
"mcpServers": {
"mapbox-mcp-server": {
"command": "node",
"args": ["/absolute/path/to/mapbox-mcp-server/build/index.js"],
"env": {
"MAPBOX_ACCESS_TOKEN": "your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MAPBOX_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.