MCP Devkit Server logo

MCP Devkit Server

Manage Mapbox styles, tokens, validation, and local geospatial processing through MCP.

Install MCP Devkit 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-devkit-server": {
      "command": "npx",
      "args": [
        "-y",
        "@mapbox/mcp-devkit-server"
      ],
      "env": {
        "MAPBOX_ACCESS_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

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

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

mcp-devkit-server connects AI assistants to Mapbox developer APIs through MCP tools for style and token management, feedback, validation, and local processing. It can list, create, retrieve, update, delete, and preview Mapbox styles, while offline validation checks style JSON against the Mapbox Style Specification. Use it when an agent needs to inspect or modify Mapbox styles or perform supported geospatial development tasks. A hosted endpoint and local packaging options support different deployment setups.

Use cases

  • Manage Mapbox styles from an AI coding workflow
  • Validate Mapbox style JSON before deployment
  • Preview an account style in a browser
  • Inspect Mapbox Streets v8 fields and layer mappings
  • Convert coordinates or process GeoJSON locally

Key features

  • Mapbox style CRUD operations
  • Style preview URL generation
  • Offline Mapbox style validation
  • Mapbox token management
  • Reference resources for styles and Streets v8
  • Local geospatial and style-processing tools

Tools40

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

Self-reported~572 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 1d ago

Recent health check succeeded.

17/17 checks healthy over the last 59d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

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

Adoption & maintenance

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

GitHub stars62Stargazers on the source repository.
npm downloads5.3kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Tools exposed40Callable tools this server registers over MCP.

How MCP Devkit Server works

What mcp-devkit-server does

mcp-devkit-server gives MCP-compatible AI assistants access to selected Mapbox developer operations. Its main focus is Mapbox style management: agents can inspect an account's styles, create new styles from a Mapbox style specification, retrieve and update existing styles, remove styles, and generate browser preview URLs.

The package also includes token-management and feedback tools, reference resources for Mapbox style and Streets v8 concepts, and local processing tools listed for GeoJSON preview, coordinate conversion, bounding boxes, style comparison, and style optimization. A separate validation capability checks style JSON without needing Mapbox API access.

How it works

The server exposes its operations through the Model Context Protocol. API-backed operations use the Mapbox access token supplied to the server, and individual operations enforce their required token scopes. For example, listing styles uses styles:list; creating, updating, or deleting styles uses styles:write; retrieving a style uses styles:download.

Preview generation obtains the first available public token from the account and uses it to construct a preview URL. That operation requires tokens:read plus a public token with styles:read. Style validation runs offline and returns validation messages, severity levels, optional JSON paths and suggestions, and a style summary that can include feature counts and geometry types.

Reference material is available as MCP resources, including the Mapbox style-layer specification, Streets v8 field definitions, token-scope guidance, and mappings between Streets v8 source layers and compatible GL JS layer types.

Setup and configuration

A Mapbox account and access token are required for API-backed use. Set the token in MAPBOX_ACCESS_TOKEN, then grant the scopes needed by the operations your agent will call. Token management requires tokens:read and tokens:write, while feedback access requires user-feedback:read.

The server can run through a local developer-tool integration or the hosted MCP endpoint at https://mcp-devkit.mapbox.com/mcp. Supported setup documentation covers Claude Code, Claude Desktop, Cursor, and Visual Studio Code. It can also be packaged as a DXT desktop extension; the package includes the built server, metadata, and configuration for the Mapbox token.

Tools and capabilities

  • Manage Mapbox styles with list, create, retrieve, update, delete, and preview operations.
  • Validate Mapbox style JSON against required fields, source and layer types, references, and common configuration issues.
  • Create and list Mapbox access tokens through token-management tools.
  • Expose Mapbox style, Streets v8, token-scope, and layer-type reference resources.
  • Use local tools for GeoJSON preview, coordinate conversion, bounding boxes, style comparison, and style optimization.
  • Inspect style expressions involving data access, lookup, decisions, mathematics, strings, types, and camera values.

Limitations and notes

Token scope requirements differ by operation, so a token that works for one style action may fail for another. Preview generation also depends on having at least one public token with styles:read. Offline validation does not require API access or token scopes, but it validates the supplied style JSON rather than making changes to a Mapbox account.

Reviews

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

Frequently Asked Questions about MCP Devkit Server

mcp-devkit-server is an MCP server that connects AI assistants to Mapbox developer APIs and local Mapbox-processing tools. Its main capabilities include listing, creating, retrieving, updating, deleting, previewing, and validating Mapbox styles, along with token management, reference resources, and selected geospatial utilities.

Use one of its documented local developer-tool integrations, the hosted endpoint, or package it as a DXT extension. The hosted endpoint is https://mcp-devkit.mapbox.com/mcp. Local DXT packaging uses the DXT CLI after building the server.

Set `MAPBOX_ACCESS_TOKEN` to a Mapbox access token for API-backed operations. The token must include the scopes required by the tools you call, such as `styles:list`, `styles:write`, or `styles:download`.

Yes, Cursor is one of the documented developer-tool integrations. Configure Cursor to connect to the local server or use the hosted MCP endpoint, then provide the required Mapbox access token.

Yes, style validation runs offline and does not require API access or token scopes. It checks the supplied Mapbox style JSON and returns errors, warnings, informational messages, and style summary data.

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 Devkit Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-devkit-server?style=directory)](https://allmcps.com/mcp/mcp-devkit-server)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-devkit-server"><img src="https://allmcps.com/api/badge/mcp-devkit-server?style=directory" alt="MCP Devkit Server on AllMCPs" /></a>