MCP Docs Server logo

MCP Docs Server

Searches and retrieves Mapbox documentation, API references, guides, and style specifications through MCP without a Mapbox token.

Install MCP Docs Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-docs-server": {
      "command": "npx",
      "args": [
        "-y",
        "@mapbox/mcp-docs-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

mcp-docs-server MCP server connects AI assistants to searchable Mapbox documentation and reference content without requiring a Mapbox access token. Its search tool returns ranked pages across APIs, SDKs, GL JS, Style Spec, Studio, Search JS, Tilesets, and other Mapbox products, while document tools retrieve one or many full pages. It also exposes reference resources covering APIs, SDKs, guides, examples, styles, token scopes, and tileset fields. Use it when an agent needs current Mapbox implementation guidance or detailed reference content rather than access to Mapbox account data.

Use cases

  • Search Mapbox API documentation from an AI coding assistant
  • Retrieve full pages about GL JS, styles, or SDKs
  • Fetch several related Mapbox reference pages in one call
  • Look up style-layer properties and Streets v8 fields

Key features

  • Natural-language Mapbox documentation search
  • Single-page document retrieval by URL
  • Batch retrieval for up to 20 pages
  • MCP resources for APIs, SDKs, guides, and examples
  • Hosted, npx, Docker, and source-based setup
  • No Mapbox access token required

Tools3

What MCP Docs Server lets your agent do. Expand a tool for its parameters.

Verified live~472 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

12/12 checks healthy over the last 57d

What it can do

From the 3 tools this server returned when we ran it; 3 declare their own safety hints.

Makes network requests · 3Read-only tools · 3
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age227 days
Maintainers28

Observed 2026-10-31 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @mapbox/mcp-docs-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.

How MCP Docs Server works

What mcp-docs-server does

mcp-docs-server gives MCP-compatible AI clients access to Mapbox documentation through a hosted service or a locally run package. It covers Mapbox API references, GL JS, the Help Center, Style Spec, Studio, Search JS, iOS and Android Maps and Navigation SDKs, and Tilesets.

The server is intended for documentation lookup. It can help an agent locate relevant pages, retrieve complete page content, inspect API parameters and rate limits, consult SDK guidance, and look up style-layer properties or Streets v8 fields. Documentation access does not require a Mapbox access token.

How it works

search_mapbox_docs_tool accepts a keyword or natural-language query and returns ranked results with page titles, URLs, and descriptions. After finding a relevant result, an agent can use get_document_tool to retrieve the complete page by URL.

For several related pages, batch_get_documents_tool fetches up to 20 URLs in one call. The response contains an entry for each requested page; a failed fetch reports an error for that page without aborting the entire batch.

The server also publishes MCP resources that clients can read on demand. These include REST API references, SDK and client-library documentation, tutorials, examples, product and pricing references, style-layer definitions, Streets v8 fields, token scopes, and layer-type mappings. HTTP requests use a shared pipeline with one-hour caching.

Setup and configuration

The hosted endpoint can be connected without installing the package:

config.json
{
  "mcpServers": {
    "mapbox-docs": {
      "url": "https://mcp-docs.mapbox.com/mcp"
    }
  }
}

For a local stdio setup, run the package with npx:

config.json
{
  "mcpServers": {
    "mapbox-docs": {
      "command": "npx",
      "args": ["-y", "@mapbox/mcp-docs-server"]
    }
  }
}

Docker is also supported. Build the repository image or pull mapbox/mcp-docs-server, then configure the client to run docker run --rm -i mapbox/mcp-docs-server. Running from source requires Node.js 22 or newer and npm; install dependencies, build the project, and start dist/esm/index.js with Node.

The documented client configurations cover Claude Code, Claude Desktop, Cursor, and VS Code. No Mapbox credential environment variable is needed for the documentation tools.

Tools and capabilities

  • Search Mapbox content with natural-language or keyword queries.
  • Retrieve a complete documentation page from its URL.
  • Fetch up to 20 documentation pages in one batch.
  • Read structured MCP resources for APIs, SDKs, guides, examples, styles, tilesets, and token scopes.
  • Use TypeScript output built in both ESM and CommonJS formats.

Limitations and notes

The batch operation is limited to 20 pages per call. Search returns result metadata rather than complete page content, so a follow-up document request is needed to read a full result. The server provides documentation and reference material; its documented tools do not require a Mapbox access token.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Docs Server

mcp-docs-server is an MCP server that connects AI assistants to Mapbox documentation through search_mapbox_docs_tool, get_document_tool, and batch_get_documents_tool. It also exposes Mapbox reference resources for API references, guides, style specifications, SDK documentation, and related reference content. No Mapbox access token is required.

You can connect to the hosted endpoint, run the package with npx, use Docker, or build it from source. The hosted URL is https://mcp-docs.mapbox.com/mcp; source builds require Node.js 22 or newer and npm.

Yes, mcp-docs-server works with Cursor. Add either the hosted URL or a local stdio configuration to Cursor's MCP settings; Docker can also be configured as the local command.

Use search_mapbox_docs_tool with a keyword or natural-language query. It returns ranked titles, URLs, and descriptions across Mapbox documentation areas, after which get_document_tool can retrieve a complete result page.

Yes, batch_get_documents_tool fetches up to 20 documentation URLs in one call. Individual failures are returned as errors for the affected pages without causing the whole batch request to fail.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Docs Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-docs-server?style=directory)](https://allmcps.com/mcp/mcp-docs-server)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-docs-server"><img src="https://allmcps.com/api/badge/mcp-docs-server?style=directory" alt="MCP Docs Server on AllMCPs" /></a>