Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

MCP Devkit Server

by mapboxversion 0.9.0i★ –iComputer or cloud
Registry nameio.github.mapbox/mcp-devkit-server

Install

Overview

Description from the maker (original English)

Provides AI assistants with direct access to Mapbox developer APIs and documentation.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: MAPBOX_ACCESS_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: MAPBOX_ACCESS_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://mcp-devkit.mapbox.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "devkit": {
      "command": "npx",
      "args": [
        "-y",
        "@mapbox/mcp-devkit-server"
      ],
      "env": {
        "MAPBOX_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http devkit https://mcp-devkit.mapbox.com/mcp

Or run it on your computer

claude mcp add devkit --env MAPBOX_ACCESS_TOKEN=your-value -- npx -y @mapbox/mcp-devkit-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "devkit": {
      "url": "https://mcp-devkit.mapbox.com/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "devkit": {
      "command": "npx",
      "args": [
        "-y",
        "@mapbox/mcp-devkit-server"
      ],
      "env": {
        "MAPBOX_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "devkit": {
      "type": "http",
      "url": "https://mcp-devkit.mapbox.com/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "devkit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mapbox/mcp-devkit-server"
      ],
      "env": {
        "MAPBOX_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://mcp-devkit.mapbox.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • MAPBOX_ACCESS_TOKEN secret required env
    Your Mapbox access token. See docs for required scopes.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account mapbox, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 836 ms (HTTP 401)

  • ✓ Pass

    Sign-in with OAuth

    Declares OAuth sign-in, so your AI app can take you to log in

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32623 servers in this category
  • Published to the registry more recently than 100% of the other 32623 servers in this category
  • Basic checks equal to or better than 100% of the other 32623 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Devkit Server safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MAPBOX_ACCESS_TOKEN

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.9.0) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Draugr

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Draugr

by draugr-dev

Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Mapbox Developer MCP Server

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.

Looking for Mapbox documentation access? Use mcp-docs-server alongside this server — it provides AI assistants with access to Mapbox documentation, guides, and API references from docs.mapbox.com.

https://github.com/user-attachments/assets/8b1b8ef2-9fba-4951-bc9a-beaed4f6aff6

Table of Contents

  • Mapbox Developer MCP Server
  • Table of Contents
  • Quick Start
  • Integration with Developer Tools
  • DXT Package Distribution
  • Creating the DXT Package
  • Hosted MCP Endpoint
  • Getting Your Mapbox Access Token
  • Tools
  • Reference Tools
  • Style Management Tools
  • Token Management Tools
  • create-token
  • list-tokens
  • Feedback Tools
  • Local Processing Tools
  • GeoJSON Preview tool (Beta)
  • Coordinate Conversion tool
  • Bounding Box tool
  • compare_styles_tool
  • Style Optimization tool
  • Resources
  • Observability \& Tracing
  • Features
  • Quick Start with Jaeger
  • Supported Backends
  • Documentation
  • Environment Variables
  • Development
  • Testing
  • Tool Snapshot Tests
  • Inspecting Server
  • Using Node.js
  • Using Docker
  • Creating New Tools
  • Environment Variables
  • VERBOSE_ERRORS
  • Troubleshooting
  • Release Process
  • Contributing

Quick Start

Integration with Developer Tools

Get started by integrating with your preferred AI development environment:

  • Claude Code Integration - Command-line development with Claude
  • Claude Desktop Integration - Desktop application integration
  • Cursor Integration - Cursor IDE integration
  • VS Code Integration - Visual Studio Code with GitHub Copilot
DXT Package Distribution

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.

Creating the DXT Package

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:

  • Pre-built server code (dist/esm/index.js)
  • Server metadata and configuration
  • User configuration schema for the Mapbox access token
  • Automatic environment variable setup
Hosted MCP Endpoint

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.

Getting Your Mapbox Access Token

A Mapbox access token is required to use this MCP server.

  1. Sign up for a free Mapbox account at mapbox.com/signup
  2. Navigate to your Account page
  3. Create a new token with the required scopes for your use case

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:

  • Reading styles requires styles:read scope
  • Creating styles requires styles:write scope
  • Managing tokens requires tokens:read and tokens:write scopes
  • Accessing feedback requires user-feedback:read scope

Tools

Reference Tools

Reference data is exposed as MCP Resources (see Resources section). MCP clients that support the resources protocol can access them directly.

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 properties
  • `resource://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 operations
  • `resource://mapbox-layer-type-mapping` - Mapping of Mapbox Streets v8 source layers to compatible GL JS layer types, with common usage patterns

Example prompts:

  • "What fields are available for the landuse layer?"
  • "Show me the token scopes reference"
  • "What layer type should I use for roads?"
  • "Get the Streets v8 fields reference"
  • "What scopes do I need to display a map?"
Style Management Tools

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 →](./docs/STYLE_BUILDER.md)

ListStylesTool - List all styles for a Mapbox account

  • Input: limit (optional - max number of styles), start (optional - pagination token)
  • Returns: Array of style metadata with optional pagination info

CreateStyleTool - Create a new Mapbox style

  • Input: name, style (Mapbox style specification)
  • Returns: Created style details with ID

RetrieveStyleTool - Retrieve a specific style by ID

  • Input: styleId
  • Returns: Complete style specification

UpdateStyleTool - Update an existing style

  • Input: styleId, name (optional), style (optional)
  • Returns: Updated style details

DeleteStyleTool - Delete a style by ID

  • Input: styleId
  • Returns: Success confirmation

PreviewStyleTool - Generate preview URL for a Mapbox style using an existing public token

  • Input: styleId, title (optional), zoomwheel (optional), zoom (optional), center (optional), bearing (optional), pitch (optional)
  • Returns: URL to open the style preview in browser
  • Note: This tool automatically fetches the first available public token from your account for the preview URL. Requires at least one public token with styles:read scope.

ValidateStyleTool - Validate Mapbox style JSON against the Mapbox Style Specification

  • Input: style (Mapbox style JSON object or JSON string)
  • Returns: Validation results including errors, warnings, info messages, and style summary
  • Performs comprehensive offline validation checking:
  • Required fields (version, sources, layers)
  • Valid layer and source types
  • Source references and layer IDs
  • Common configuration issues
  • Note: This is an offline validation tool that doesn't require API access or token scopes

⚠️ 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.

  • ListStylesTool: Requires styles:list scope
  • CreateStyleTool: Requires styles:write scope
  • RetrieveStyleTool: Requires styles:download scope
  • UpdateStyleTool: Requires styles:write scope
  • DeleteStyleTool: Requires styles:write scope
  • PreviewStyleTool: Requires tokens:read scope (to list tokens) and at least one public token with styles:read scope

Note: The username is automatically extracted from the JWT token payload.

Example prompts:

  • "Can you create a Christmas themed Style for me?"
  • "Please generate a preview link for this style"
  • "Can you change the background to snow style?"
Token Management Tools
create-token

Create a new Mapbox access token with specified scopes and optional URL restrictions.

Parameters:

  • note (string, required): Description of the token
  • scopes (array of strings, required): Array of scopes/permissions for the token. Must be valid Mapbox scopes (see below)
  • allowedUrls (array of strings, optional): URLs where the token can be used (max 100)
  • expires (string, optional): Expiration time in ISO 8601 format (maximum 1 hour in the future)

Available Scopes:

Available scopes for public tokens:

  • styles:tiles - Read styles as raster tiles
  • styles:read - Read styles
  • fonts:read - Read fonts
  • datasets:read - Read datasets
  • vision:read - Read Vision API

Example:

{

"note": "Development token for my app", "scopes": ["styles:read", "fonts:read"], "allowedUrls": ["https://myapp.com"] }

Example prompts:

  • "Create a new Mapbox token for my web app with styles:read and fonts:read permissions"
  • "Generate a token that expires in 30 minutes with styles:tiles and vision:read scopes"
  • "Create a restricted token that only works on https://myapp.com with styles:read, fonts:read, and datasets:read"
list-tokens

List Mapbox access tokens for the authenticated user with optional filtering and pagination.

Parameters:

  • default (boolean, optional): Filter to show only the default public token
  • limit (number, optional): Maximum number of tokens to return per page (1-100)
  • sortby (string, optional): Sort tokens by "created" or "modified" timestamp
  • start (string, optional): The token ID after which to start the listing (when provided, auto-pagination is disabled)
  • usage (string, optional): Filter by token type: "pk" (public)

Pagination behavior:

  • When no start parameter is provided, the tool automatically fetches all pages of results
  • When a start parameter is provided, only the requested page is returned (for manual pagination control)

Example:

{

"limit": 10, "sortby": "created", "usage": "pk" }

Example prompts:

  • "List all my Mapbox tokens"
  • "Show me my public tokens sorted by creation date"
  • "Find my default public token"
  • "List the 5 most recently modified tokens"
  • "Show all public tokens in my account"
Feedback Tools

Access user feedback items from the Mapbox Feedback API. These tools allow you to retrieve and view user-reported issues, suggestions, and feedback about map data, routing, and POI details.

list_feedback_tool - List user feedback items with comprehensive filtering, sorting, and pagination options.

Parameters:

  • feedback_ids (array of UUIDs, optional): Filter by one or more feedback item IDs
  • after (string, optional): Cursor from a previous response for pagination
  • limit (number, optional): Maximum number of items to r

Only the beginning is shown; read the rest in the repo

Ask PopNx