Labsco
MCP SERVER · OFFICIAL PROJECT

Mapbox Docs MCP Server

by mapbox ↗

Mapbox's documentation, searchable from inside your assistant, with whole pages pulled back on demand.

Development✓ Popular vendor Official

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

Nothing to hand over, and nothing it can change.

The hosted endpoint answers anonymous callers, there is no account for it to be attached to, and every tool is read-only — so the only question left is whether you work with Mapbox often enough to want its documentation in the conversation. The one limit worth knowing is coverage: search is built by indexing the product-level llms.txt files Mapbox publishes, so a part of the docs tree that publishes no such file does not come back in results, and the pages describing this server are themselves among the ones that do not.

What it is

Mapbox runs four MCP servers; this is the documentation one. It gives an AI assistant full-text search across everything Mapbox publishes as documentation, plus the complete text of any documentation page it turns up. It reads public web pages and nothing else — the geocoding and directions server and the map-styling server are separate servers on separate endpoints.

What you get

  • Full-text search over Mapbox's documentation: the API reference, GL JS, the Help Center, the Style Specification, Studio, Search JS, the iOS and Android Maps and Navigation SDKs, and Tilesets. Results come back ranked, with titles, URLs and descriptions — up to 20 per query, 5 by default.
  • The complete content of a documentation page by URL, not an excerpt. It takes mapbox.com and docs.tilestream.net addresses.
  • Up to 20 pages in one call, with each page's result carried separately, so one URL that fails comes back as an error beside the pages that worked instead of failing the whole request.
  • Reference material the assistant can read directly rather than search for: the style layer types with their paint and layout properties, Streets v8 field definitions with their enumerated values, the token scope reference, and a Streets v8 to GL JS layer compatibility matrix.

Requirements

Nothing — no account, no sign-up, no access token, no API key. You need an MCP client that can reach a remote endpoint, and that is the whole list. Node.js 22 or later comes into it only if you decide to run your own copy from the npm package instead of using Mapbox's hosted endpoint.

Setup effort

Paste a URL — add the endpoint to your client