mcp-devkit

This MCP server provides AI assistants with direct access to Mapbox developer APIs. It exposes tools and workflows that let you search Mapbox docs, inspect reference data, manage tokens and styles, and run local processing tasks like GeoJSON previews and coordinate transformations. The server is designed to be used by large language models and agents to perform Mapbox operations in-context, enabling capabilities such as reading Mapbox styles, creating tokens with the necessary scopes, and validating style configurations. Use the hosted or local endpoint as the integration point for your AI tooling, and supply a Mapbox access token via environment variables to authorize requests.

To interact with the server, configure it in your MCP client using the supplied endpoint. Tools such as get_latest_mapbox_docs_tool, get_reference_tool, and style management tools (Style Builder, ListStylesTool, CreateStyleTool) are available. For local processing, you can leverage GeoJSON Preview, Coordinate Conversion, Bounding Box computations, and style comparison and optimization tools. The server is organized to provide both reference/documentation access and operational actions against Mapbox services, all mediated through MCP tool interfaces and prompts.

Prerequisites:

• Node.js (LTS version) and npm installed
• Git (optional, for cloning the repository)
• Mapbox Access Token with appropriate scopes for the tools you plan to use

Step-by-step installation:

1. Clone the repository git clone https://github.com/mapbox/mapbox-mcp-devkit-server.git cd mapbox-mcp-devkit-server

2. Install dependencies npm install

3. Build the server (if a build step is required by the project) npm run build

4. Run the server locally (using a Mapbox access token) MAPBOX_ACCESS_TOKEN=YOUR_TOKEN_HERE npm start

5. Verify the server is running Open http://localhost:3000/health or the configured port to ensure the MCP server is responding

Notes:

• If you publish a DXT package, ensure manifest.json and dist/esm/index.js exist as described in the docs.
• If you deploy with a container or cloud service, adjust the command to point to your built entry point and surface the MAPBOX_ACCESS_TOKEN securely.

Tips and common issues:

• Ensure MAPBOX_ACCESS_TOKEN has the required scopes for the operations you intend to perform (styles:read/write, tokens:read/write, user-feedback:read, etc.).
• When packaging as DXT, the server bundle will include a user configuration schema for Mapbox access tokens.
• If you see missing tool references, verify you have the latest manifest.json and that the built dist/esm/index.js path exists in your deployment package.
• For hosted MCP endpoints, update client configurations to point to the hosted URL rather than the local endpoint.
• For development, test each tool individually (get_latest_mapbox_docs_tool, get_reference_tool, Style Builder, etc.) to ensure proper API access and token scopes.