Labsco
MCP SERVER · OFFICIAL PROJECT

Mapbox DevKit MCP Server

by mapbox ↗

Puts your Mapbox styles, your token list, your users' map reports and a set of offline style and GeoJSON checks within an agent's reach.

Development✓ Popular vendor Official

This server also ships inside Mapbox Agent Skills — a plugin that installs it already configured.

It can delete styles in your account, and there is no read-only mode.

Four of the tools here write: one creates a style, one changes a style, one deletes a style by ID, and the conversational builder does both — all under the styles:write permission the browser sign-in grants. The hosted endpoint has no per-tool switch, so the ways to stop it are taking it out of your client's config or revoking the grant on your Mapbox account. Mapbox runs four MCP servers and this is the one for working on your own account: if you came for directions, geocoding or a search across Mapbox's documentation, those tools are on the other servers.

What it is

The developer-workflow Mapbox server: it acts on your own Mapbox account — the styles in it, the access tokens listed on it, the map problems your users reported against it — and adds a set of checks that run locally, with no API call. Mapbox hosts it, so there is nothing for you to run. Documentation search used to be part of this server and is not any more; Mapbox moved those tools out to a separate Mapbox Docs MCP Server.

What you get

  • The styles in your account, end to end: list them, retrieve one by ID, create, change and delete — or describe the look you want and have it built conversationally.
  • A live preview of a style at a centre, zoom, bearing and pitch you choose, and a side-by-side URL that puts two styles next to each other.
  • Validation that needs no API call: style JSON against the Mapbox schema, style expressions, GeoJSON structure and ring closure, and WCAG 2.1 AA/AAA contrast between text and background colours.
  • A deep diff of two styles that reports every addition, removal and change with its JSON path, and an optimiser that strips unused sources, duplicate layers and empty layers and reports the file-size change.
  • The map problems your users reported, filtered by status, category, date or trace ID, plus any single report by its UUID.
  • Point queries into Mapbox tilesets: what vector or raster data sits at a given coordinate.
  • Coordinate work on the side: WGS84 to Web Mercator and back, a bounding box from GeoJSON features, a bounding box for a country by its ISO 3166-1 code, and a geojson.io link for a file.
  • A read-only list of the access tokens on your account, with their types, scopes and dates, filterable by type, creation date or modification status.

Requirements

A Mapbox account, and a client that can reach a remote HTTP endpoint. There is no key to paste or store: the first time your client connects, Mapbox opens a browser sign-in, and from then on the server acts on that account.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen