mapbox-docs
OfficialSummary: This server gives AI assistants token-free, read-only access to Mapbox documentation — searching it, fetching full pages, and reading bundled reference resources.
Search Mapbox docs (
search_mapbox_docs_tool) — keyword or natural-language queries across API reference, GL JS, Help Center, Style Spec, Studio, Search JS, iOS/Android Maps & Navigation SDKs, and Tilesets; returns ranked titles, URLs, and descriptions (1–20 results, default 5).Fetch a single doc page (
get_document_tool) — retrieves the full content of any mapbox.com documentation URL.Fetch up to 20 pages at once (
batch_get_documents_tool) — more efficient than repeated single calls; individual failures return error messages instead of failing the whole batch.Read on-demand reference resources — API reference, SDK/client library docs, guides & tutorials, code examples & demos, tilesets/data/accounts/pricing reference, style layer paint/layout properties, Mapbox Streets v8 fields, token scopes, and layer-type-to-property mapping.
Usage properties — all tools are read-only, idempotent, non-destructive, and require no Mapbox access token; can be hosted, run via npx, Docker, or locally from source.
Provides tools to search and fetch Mapbox documentation, including API references, SDK docs, guides, examples, and style references.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mapbox-docs How do I add a custom layer to a Mapbox style?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mapbox MCP Documentation Server
A Model Context Protocol (MCP) server that gives AI assistants instant access to Mapbox documentation and reference materials — no Mapbox access token required.
Quick Start
Hosted (no install required)
Connect directly to the hosted endpoint — nothing to install or maintain:
Claude Code / Claude Desktop / Cursor / VS Code
{
"mcpServers": {
"mapbox-docs": {
"url": "https://mcp-docs.mapbox.com/mcp"
}
}
}npx (runs locally, no install)
Claude Code — run claude mcp add:
claude mcp add mapbox-docs -- npx -y @mapbox/mcp-docs-serverClaude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"mapbox-docs": {
"command": "npx",
"args": ["-y", "@mapbox/mcp-docs-server"]
}
}
}Cursor / VS Code — add the same mcpServers block to your editor's MCP settings file.
Docker
Build the image:
docker build -t mapbox/mcp-docs-server .Or pull from the registry:
docker pull mapbox/mcp-docs-serverClaude Desktop / Cursor / VS Code — configure your MCP client to run the container:
{
"mcpServers": {
"mapbox-docs": {
"command": "docker",
"args": ["run", "--rm", "-i", "mapbox/mcp-docs-server"]
}
}
}Local (from source)
git clone https://github.com/mapbox/mcp-docs-server.git
cd mcp-docs-server
npm install
npm run buildClaude Desktop / Cursor / VS Code:
{
"mcpServers": {
"mapbox-docs": {
"command": "node",
"args": ["/absolute/path/to/mcp-docs-server/dist/esm/index.js"]
}
}
}Related MCP server: Mapbox MCP Server
Tools
get_document_tool — Fetches the full content of a specific Mapbox documentation page by URL. Use this to follow a link from a resource and retrieve the complete page content.
Example prompts:
"What Mapbox APIs are available?"
"How do I add a custom layer to a Mapbox style?"
"What's the latest Mapbox GL JS version?"
batch_get_documents_tool — Fetches multiple Mapbox documentation pages in a single call (max 20). More efficient than calling get_document_tool multiple times. Failed pages include an error message rather than failing the whole batch.
search_mapbox_docs_tool — Searches Mapbox documentation across API reference, GL JS, Help Center, Style Spec, Studio, Search JS, iOS/Android Maps and Navigation SDKs, and Tilesets, returning ranked page URLs and descriptions. Use this to find relevant documentation before fetching full pages with get_document_tool or batch_get_documents_tool.
Example prompts:
"Find docs about camera animation"
"Search for geocoding API examples"
"What documentation exists for custom layers?"
Resources
MCP resources expose reference data that AI assistants can read on demand:
Resource URI | Contents |
| REST API reference docs (endpoints, parameters, rate limits) |
| SDK and client library docs (iOS, Android, Flutter, web) |
| Tutorials, how-tos, and guides |
| Code examples, API playgrounds, and interactive demos |
| Tilesets, data products, accounts, and pricing reference |
| Style layer reference (paint/layout properties for all layer types) |
| Mapbox Streets v8 tileset field reference |
| All available Mapbox token scopes with descriptions |
| Mapping of Mapbox layer types to their properties |
Development
Prerequisites
Node.js >= 22
npm
Setup
git clone https://github.com/mapbox/mcp-docs-server.git
cd mcp-docs-server
npm installCommands
npm run build # Compile TypeScript (ESM + CJS)
npm test # Run test suite (vitest)
npm run lint # ESLint
npm run format # Prettier check
npm run format:fix # Prettier auto-fix
npm run inspect:build # Launch MCP Inspector against built server
npm run inspect:dev # Launch MCP Inspector against source (tsx)Architecture
The server is a TypeScript MCP server using @modelcontextprotocol/sdk with a dual ESM/CJS build via tshy.
Tools extend
BaseTool<InputSchema, OutputSchema>insrc/tools/Resources extend
BaseResourceinsrc/resources/No Mapbox access token required for documentation tools
HTTP requests use a shared
httpPipelinewith 1-hour caching
Creating a New Tool
Create a directory
src/tools/my-tool/Add
MyTool.input.schema.ts(Zod schema),MyTool.output.schema.ts, andMyTool.ts(extendsBaseTool)Register in
src/tools/toolRegistry.tsAdd tests in
test/tools/my-tool/
Contributing
Please read CONTRIBUTING.md and VISION.md before submitting a pull request. Contributors using AI coding assistants should also review:
CLAUDE.md — for Claude Code
AGENTS.md — for other AI coding assistants (Cursor, Copilot, Aider, etc.)
License
MIT — see LICENSE
Available Tools
3 toolsbatch_get_documents_toolBatch Get Mapbox Documents ToolARead-onlyIdempotentInspect
Fetch the full content of multiple Mapbox documentation pages in a single call (max 20). More efficient than calling get_document_tool multiple times. Returns an array of results — failed pages include an error message rather than failing the whole batch.
Inputs: urls (required).
get_document_toolGet Mapbox Document ToolARead-onlyIdempotentInspect
Fetch the full content of a specific Mapbox documentation page by URL. Use this after search_mapbox_docs_tool to follow a link from the search results and retrieve the complete page content. For fetching multiple pages at once, use batch_get_documents_tool instead.
Inputs: url (required).
search_mapbox_docs_toolSearch Mapbox Docs ToolARead-onlyIdempotentInspect
Search Mapbox documentation by keyword or natural language query. Searches across API reference, GL JS, Help Center, Style Spec, Studio, Search JS, iOS/Android Maps and Navigation SDKs, and Tilesets. Returns ranked results with titles, URLs, and descriptions. Use get_document_tool to fetch the full content of a result page.
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: search to find pages, get_document_tool to fetch one page, batch_get_documents_tool to fetch many. The descriptions explicitly cross-reference each other and state when to prefer one over the other, leaving no real ambiguity.
All names are snake_case and end in the same _tool suffix, following a verb_object pattern (get_document, search_mapbox_docs). The only deviation is the 'batch_' prefix on batch_get_documents_tool, which is a minor and readable variation.
Three tools is on the thin side, but it maps cleanly to the narrow purpose of a documentation search-and-retrieve server. Batch fetching earns its place alongside the single-fetch tool, so nothing feels redundant.
Search plus single and batch retrieval covers the core documentation workflow end to end, including partial-failure handling in the batch call. Minor gaps exist (no explicit pagination or listing/index tool for browsing all docs), but agents can work around these via search.
Maintenance
Related MCP Connectors
Provides AI assistants with direct access to Mapbox developer APIs and documentation.
Routing, geocoding, places, matrix and map tools for location-aware AI workflows.
Geospatial intelligence with Mapbox APIs like geocoding, POI search, directions, isochrones, etc.
Provide your AI coding tools with token-efficient access to up-to-date technical documentation for…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI applications with geospatial intelligence through Mapbox APIs, enabling geocoding, POI search, routing, travel time analysis, isochrone generation, and static map creation for location-aware functionality.4,065 npmBSD 3-Clause

Mapbox MCP Serverofficial
AlicenseAqualityBmaintenanceProvides geospatial intelligence to AI agents through Mapbox APIs, enabling geocoding, routing, POI search, map images, and offline spatial calculations.284,065 npm367MIT- AlicenseAqualityBmaintenanceEnables AI assistants to interact with Mapbox developer APIs for style management, token management, and local processing tasks like GeoJSON preview and coordinate conversion.231,329 npm62MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access Mapbox location services for geocoding, POI search, multi-modal routing, travel time analysis, isochrones, map matching, and interactive/static map rendering through natural language.4,065 npmMIT