Provides tools to search and fetch Mapbox documentation, including API references, SDK docs, guides, examples, and style references.
Click on "Install 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.
A Model Context Protocol (MCP) server that gives AI assistants instant access to Mapbox documentation and reference materials — no Mapbox access token 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"
}
}
}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.
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"]
}
}
}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
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 using Algolia full-text search and returns matching page URLs and excerpts. 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?"
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 |
Node.js >= 22
npm
git clone https://github.com/mapbox/mcp-docs-server.git
cd mcp-docs-server
npm installnpm 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)The server is a TypeScript MCP server using @modelcontextprotocol/sdk with a dual ESM/CJS build via tshy.
Tools extend BaseTool<InputSchema, OutputSchema> in src/tools/
Resources extend BaseResource in src/resources/
No Mapbox access token required for documentation tools
HTTP requests use a shared httpPipeline with 1-hour caching
Create a directory src/tools/my-tool/
Add MyTool.input.schema.ts (Zod schema), MyTool.output.schema.ts, and MyTool.ts (extends BaseTool)
Register in src/tools/toolRegistry.ts
Add tests in test/tools/my-tool/
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.)
MIT — see LICENSE
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.
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | Array of Mapbox documentation page URLs to fetch (max 20). All must be mapbox.com URLs. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (readOnlyHint, idempotentHint), the description reveals critical behavior: partial failures are handled gracefully—failed pages return error messages instead of failing the whole batch. This adds significant value for an agent deciding how to handle errors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two terse sentences that pack maximum information: purpose, efficiency comparison, batch limit, and return behavior. No wasted words; each sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately explains return format (array of results with error messages on failure). Combined with annotations and input schema, it covers all behavioral aspects needed for safe and effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although schema coverage is 100%, the description adds the important constraint that all URLs must be mapbox.com URLs, which is not enforced by the schema's format: uri. This domain restriction is essential for correct usage and goes beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Fetch the full content of multiple Mapbox documentation pages' with a specific verb and resource. It distinguishes itself from sibling get_document_tool by noting efficiency and from search_mapbox_docs_tool by focusing on fetching full content rather than searching.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'More efficient than calling get_document_tool multiple times,' directly guiding the agent to prefer this tool for batch requests. Also sets a clear limit (max 20) and mentions return behavior, leaving no ambiguity about appropriate use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Fetch the full content of a specific Mapbox documentation page by URL. Use this after get_latest_mapbox_docs_tool to follow a link from the index and retrieve the complete page content. For fetching multiple pages at once, use batch_get_documents_tool instead.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL of a Mapbox documentation page to fetch. Must be a mapbox.com URL (e.g. https://docs.mapbox.com/api/search/geocoding/). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, etc., which the description does not contradict. The description adds that it fetches 'full content' but does not provide additional behavioral details like response format or potential limits. Given the strong annotations, this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each serving a distinct purpose: stating the action, providing sequential usage, and noting an alternative. No filler, front-loaded with the primary function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple single-parameter schema and comprehensive annotations, the description adequately explains the tool's role and relationship to siblings. Does not cover error handling or output details, but for a fetch tool this is acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with the 'url' parameter having a clear description. The tool description adds no new meaning beyond 'by URL'. Baseline score of 3 applies as the schema already documents the parameter well.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Fetch the full content of a specific Mapbox documentation page by URL', with a specific verb and resource. It distinguishes itself from the sibling 'batch_get_documents_tool' by noting its role for single-page retrieval and references the sequential tool 'get_latest_mapbox_docs_tool'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises use after 'get_latest_mapbox_docs_tool' and contrasts with 'batch_get_documents_tool' for multiple pages, providing clear context. Missing explicit mention of when not to use (e.g., when searching), but still strong guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query for Mapbox documentation (e.g. "add a marker", "camera animation", "geocoding API"). | |
| limit | No | Maximum number of results to return (1–20, default 5). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only and idempotent hints. The description adds that results are ranked with titles, URLs, and descriptions, filling the gap of no output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences precisely define the tool's action, scope, output format, and related tool usage with no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given full schema coverage, read-only annotations, and no output schema, the description provides sufficient context for a search tool, though could mention result ordering.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers both parameters fully with descriptions. The description mentions 'keyword or natural language query' but adds no new parameter semantics beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches Mapbox documentation by keyword or natural language query, and lists specific documentation sources (API reference, GL JS, etc.), distinguishing it from sibling fetch tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly directs users to use get_document_tool for full content, but lacks broader when-to-use or when-not-to-use guidance beyond that single sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.3.1batch_get_documents_toolget_document_toolsearch_mapbox_docs_toolEach tool has a clearly distinct purpose: search_index returns pages, get_document fetches a single page, and batch_get_documents fetches multiple. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun_tool pattern (batch_get_documents_tool, get_document_tool, search_mapbox_docs_tool), making them predictable and easy to understand.
With 3 tools, the server covers the essential operations for documentation retrieval (search, single fetch, batch fetch) without unnecessary bloat. The count is well-scoped for this purpose.
The tool set covers search, single fetch, and batch fetch effectively. However, there is no tool to list or navigate the documentation structure (e.g., get index/topics), requiring reliance on search alone. This is a minor gap.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Provides AI assistants with direct access to Mapbox developer APIs and documentation.
Mapbox geocode, directions, matrix, isochrones, map-matching, tilequery, static URL.
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…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mapbox/mcp-docs-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server