All servers / Maps / Mapbox DevKit
Mapbox DevKit
Mapbox developer tools.
Tested by ConnectATDScore 80 out of 100. Tested 2026-11-17 on package version 0.10.0. Package: @mapbox/mcp-devkit-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 12 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (87.2 seconds including download)
- Tools offered: 23
- Last published: 2026-11-11
- Weekly downloads (npm): 1,634
- License: MIT · Direct dependencies: 14
Notes
- The package runs install scripts, which execute code when you install it.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_styles_tool2 of 2 parameters describedList styles for a Mapbox account. Use limit parameter to avoid large responses (recommended: limit=5-10). Use start parameter for pagination.
create_style_tool2 of 2 parameters describedCreate a new Mapbox style
retrieve_style_tool1 of 1 parameter describedRetrieve a specific Mapbox style by ID
update_style_tool3 of 3 parameters describedUpdate an existing Mapbox style
delete_style_tool1 of 1 parameter describedDelete a Mapbox style by ID
preview_style_tool5 of 5 parameters describedGenerate a live preview of a Mapbox style. By default, auto-generates a short-lived preview token so you can view it right away — no existing token needed. Pass `share: true` with an existing public `accessToken` instead to generate a durable, shareable preview link.
style_builder_tool5 of 5 parameters describedGenerate Mapbox style JSON for creating new styles or updating existing ones. The tool intelligently resolves layer types and filter properties using Streets v8 data. You don't need exact layer names - the tool automatically finds the correct layer based on your filters. BASE STYLES: • standard: ALWAYS THE DEFAULT - Modern Mapbox Standard with best performance • Classic styles: streets-v12/light-v11/dark-v11/satellite-v9/outdoors-v12/satellite-streets-v12/navigation-day-v1/navigation-night-v1 Only use Classic when user explicitly says "create a classic style" or working with existing Classic style STANDARD STYLE CONFIG: Use standard_config to customize the basemap: • Theme: default/faded/monochrome • Light: day/night/dawn/dusk • Show/hide: labels, roads, 3D buildings • Colors: water, roads, parks, etc. LAYER ORDERING: • Layers are rendered in order - last layer in the array appears visually on top • The 'slot' parameter is OPTIONAL - by default, layer order in the array determines visibility • For Standard style, you can optionally use 'slot' to control placement: - No slot (default): Above all existing layers in the style - 'top': Behind Place and Transit labels - 'middle': Between basemap and labels - 'bottom': Below most basemap features LAYER RENDERING: • render_type controls HOW to visualize the layer (line, fill, symbol, etc.) • Most important: Use render_type:"line" for outlines/borders even on polygon features • Default "auto" picks based on geometry, but override for specific effects: - Building outlines → render_type:"line" (not fill!) - Solid buildings → render_type:"fill" or "fill-extrusion" (3D) - Road lines → render_type:"line" (auto works too) - POI dots → render_type:"circle" - Labels → render_type:"symbol" LAYER ACTIONS: • color: Apply a specific color • highlight: Make prominent • hide: Remove from view • show: Display with defaults AUTO-DETECTION: The tool automatically finds the correct layer from your filter_properties. Examples: • { class: 'park' } → finds 'landuse' layer • { type: 'wetland' } → finds 'landuse_overlay' layer • { maki: 'restaurant' } → finds 'poi_label' layer • { toll: true } → finds 'road' layer • { admin_level: 0 } → finds 'admin' layer (for country boundaries) • { admin_level: 1 } → finds 'admin' layer (for state/province boundaries) IMPORTANT LAYER NAMES: • Use "admin" for all boundaries (countries, states, etc.) • Use "building" (singular, not "buildings") • Use "road" for all streets, highways, paths If a layer type is not recognized, the tool will provide helpful suggestions showing: • All available source layers from Streets v8 • Which fields are available in each layer • Examples of how to properly specify layers and filters
geojson_preview_tool1 of 1 parameter describedGenerate a geojson.io URL to visualize GeoJSON data. Returns only the URL link.
check_color_contrast_tool4 of 4 parameters describedChecks color contrast ratios between foreground and background colors for WCAG 2.1 accessibility compliance
compare_styles_tool3 of 3 parameters describedCompares two Mapbox styles and reports differences in structure, layers, sources, and properties
optimize_style_tool2 of 2 parameters describedOptimizes Mapbox styles by removing unused sources, duplicate layers, and simplifying expressions
style_comparison_tool7 of 7 parameters describedGenerate a live side-by-side comparison of two Mapbox styles. By default, auto-generates a scoped preview token so you can compare them right away — no existing token needed. Pass `share: true` with an existing public `accessToken` instead to generate a comparison link using a token you manage yourself.
create_token_tool4 of 4 parameters describedCreate a new Mapbox public access token with specified scopes and optional URL restrictions.
list_tokens_tool5 of 5 parameters describedList Mapbox access tokens for the authenticated user with optional filtering and pagination. Returns metadata for all tokens (public and secret), but the actual token value is only included for public tokens (secret token values are omitted for security). When using pagination, the "start" parameter must be obtained from the "next_start" field of the previous response (it is not a token ID)
bounding_box_tool1 of 1 parameter describedCalculates bounding box of given GeoJSON content, returns as [minX, minY, maxX, maxY]
country_bounding_box_tool1 of 1 parameter describedGets bounding box for a country by its ISO 3166-1 country code, returns as [minX, minY, maxX, maxY].
coordinate_conversion_tool3 of 3 parameters describedConverts coordinates between WGS84 (longitude/latitude) and EPSG:3857 (Web Mercator) coordinate systems
get_feedback_tool2 of 2 parameters describedGet a single user feedback item from the Mapbox Feedback API by its unique ID. Use this tool to retrieve detailed information about a specific user-reported issue, suggestion, or feedback about map data, routing, or POI details. Requires user-feedback:read scope on the access token.
list_feedback_tool16 of 16 parameters describedList user feedback items from the Mapbox Feedback API with filtering, sorting, and pagination. Use this tool to access user-reported issues, suggestions, and feedback about map data, routing, and POI details. Supports comprehensive filtering by status, category, date ranges, trace IDs, and search text. Requires user-feedback:read scope on the access token.
tilequery_tool9 of 9 parameters describedQuery vector and raster data from Mapbox tilesets at geographic coordinates
validate_expression_tool2 of 2 parameters describedValidates Mapbox style expressions for syntax, operators, and argument correctness
validate_geojson_tool1 of 1 parameter describedValidates GeoJSON objects for correctness, checking structure, coordinates, and geometry types
validate_style_tool1 of 1 parameter describedValidates Mapbox style JSON against the Mapbox Style Specification, checking for errors, warnings, and providing suggestions for improvement
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.