by mapbox
Mapbox DevKit: Mapbox developer tools with Mapbox API access, Mapbox SDKs, tokens, docs and map styling utilities to bui
Provides AI assistants with direct access to Mapbox developer APIs for building mapping applications. Includes tools for managing map styles, access tokens, and geographic data processing.
Mapbox DevKit is an official MCP server published by mapbox that provides AI assistants with tools and capabilities via the Model Context Protocol. Mapbox DevKit: Mapbox developer tools with Mapbox API access, Mapbox SDKs, tokens, docs and map styling utilities to bui It is categorized under developer tools.
You can install Mapbox DevKit in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
MIT
Mapbox DevKit is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Mapbox DevKit reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Mapbox DevKit reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Mapbox DevKit for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
I recommend Mapbox DevKit for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Mapbox DevKit surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Strong directory entry: Mapbox DevKit surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired Mapbox DevKit into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired Mapbox DevKit into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Mapbox DevKit is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Mapbox DevKit is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 31
A Model Context Protocol (MCP) server that provides AI assistants with direct access to Mapbox developer APIs. This server enables AI models to interact with Mapbox services, helping developers build Mapbox applications more efficiently.
https://github.com/user-attachments/assets/8b1b8ef2-9fba-4951-bc9a-beaed4f6aff6
Get started by integrating with your preferred AI development environment:
This MCP server can be packaged as a DXT (Desktop Extension) file for easy distribution and installation. DXT is a standardized format for distributing local MCP servers, similar to browser extensions.
To create a DXT package:
# Install the DXT CLI tool
npm install -g @anthropic-ai/dxt
# Build the server first
npm run build
# Create the DXT package
npx @anthropic-ai/dxt pack
This will generate mcp-devkit-server.dxt using the configuration in manifest.json.
The DXT package includes:
dist/esm/index.js)For quick access, you can use our hosted MCP endpoint:
Endpoint: https://mcp-devkit.mapbox.com/mcp
For detailed setup instructions for different clients and API usage, see the Hosted MCP Server Guide. Note: This guide references the standard MCP endpoint - you'll need to update the endpoint URL to use the devkit endpoint above.
A Mapbox access token is required to use this MCP server.
For more information about Mapbox access tokens, see the Mapbox documentation on access tokens.
⚠️ IMPORTANT: Token Privileges Required
The MAPBOX_ACCESS_TOKEN environment variable is required. Each tool requires specific token scopes/privileges to function properly. For example:
styles:read scopestyles:write scopetokens:read and tokens:write scopesuser-feedback:read scopeget_latest_mapbox_docs_tool - Access the latest official Mapbox documentation directly from the source. This tool fetches comprehensive, up-to-date information about all Mapbox APIs, SDKs, and developer resources from docs.mapbox.com/llms.txt.
Example prompts:
📖 See more examples and interactive demo →
get_reference_tool - Access static Mapbox reference documentation and schemas. This tool provides essential reference information that helps AI assistants understand Mapbox concepts and build correct styles and tokens.
Note: This tool exists as a workaround for Claude Desktop's current limitation with MCP resources. Claude Desktop can see resources (via
resources/list) but doesn't automatically callresources/readto fetch their content. This tool provides the same reference data through the tool interface, which Claude Desktop does support. Other MCP clients that fully support the resources protocol can access this data directly as MCP Resources (see Resources section below).
Available References:
resource://mapbox-style-layers - Mapbox GL JS style specification reference guide covering all layer types (fill, line, symbol, circle, fill-extrusion) and their propertiesresource://mapbox-streets-v8-fields - Complete field definitions for all Mapbox Streets v8 source layers, including enumerated values for each field (useful for building filters)resource://mapbox-token-scopes - Comprehensive token scope reference explaining what each scope allows and which scopes are needed for different operationsresource://mapbox-layer-type-mapping - Mapping of Mapbox Streets v8 source layers to compatible GL JS layer types, with common usage patternsExample prompts:
Complete set of tools for managing Mapbox styles via the Styles API:
Style Builder Tool - Create and modify Mapbox styles programmatically through conversational prompts
📖 See the Style Builder documentation for detailed usage and examples →
ListStylesTool - List all styles for a Mapbox account
limit (optional - max number of styles), start (optional - pagination token)CreateStyleTool - Create a new Mapbox style
name, style (Mapbox style specification)RetrieveStyleTool - Retrieve a specific style by ID
styleIdUpdateStyleTool - Update an existing style
styleId, name (optional), style (optional)DeleteStyleTool - Delete a style by ID
styleIdPreviewStyleTool - Generate preview URL for a Mapbox style using an existing public token
styleId, title (optional), zoomwheel (optional), zoom (optional), center (optional), bearing (optional), pitch (optional)styles:read scope.ValidateStyleTool - Validate Mapbox style JSON against the Mapbox Style Specification
style (Mapbox style JSON object or JSON string)⚠️ Required Token Scopes:
All style tools require a valid Mapbox access token with specific scopes. Using a token without the correct scope will result in authentication errors.
styles:list scopestyles:write scopestyles:download scopestyles:write scopestyles:write scopetokens:read scope (to list tokens) and at least one public token with styles:read scopePrerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.