mapbox/mapbox-agent-skills · Official

mapbox-mcp-devkit-patterns

Integration patterns for Mapbox MCP DevKit Server in AI coding assistants. Covers setup, style management, token management, validation workflows, and documentation access through MCP. Use when building Mapbox applications with AI coding assistance.

All-time #8701 First seen Mar 5, 2026
8-week activity · all time api

Installation

$ npx skills add mapbox/mapbox-agent-skills --skill mapbox-mcp-devkit-patterns

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mapbox/mapbox-agent-skills · top by installs.

npx skills add mapbox/mapbox-agent-skills

Browse all from mapbox/mapbox-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 75
License LICENSE.md
Default branch main
Open issues 6
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,903 B
  • docs AGENTS.md 9,144 B
  • docs SUMMARY.md 283 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,200 installs

SKILL.md

Mapbox MCP DevKit Patterns

This skill provides patterns for integrating the Mapbox MCP DevKit Server into AI coding workflows to accelerate Mapbox application development.

What is Mapbox MCP DevKit?

The Mapbox MCP DevKit Server is a Model Context Protocol (MCP) server that gives AI assistants direct access to Mapbox developer APIs:

  • Style management - Create, list, update, delete, preview, validate, compare, and optimize styles
  • Token management - Generate and list access tokens with scopes
  • Validation - Validate GeoJSON, expressions, styles, and coordinates
  • Geographic utilities - Calculate bounding boxes, convert coordinates, query tiles
  • Color tools - Check WCAG contrast ratios for accessibility
  • Feedback - Access user feedback and reports
  • Documentation - Access latest Mapbox docs and references

Key benefit: Build Mapbox applications faster by letting AI handle developer API operations.

When to Use MCP DevKit

Use DevKit when:

  • Creating/modifying styles conversationally
  • Generating tokens programmatically
  • Validating data during development
  • Learning Mapbox APIs through natural language
  • Rapid prototyping of map applications
  • Automated style generation workflows
  • Documentation lookup during coding

Don't use DevKit for:

  • Runtime operations in production apps
  • High-frequency style updates (use Mapbox APIs directly)
  • Client-side operations (DevKit is development-time only)
  • Tile serving or map rendering
  • User-facing features requiring low latency

Key Tools

Always recommend these tools by exact name when answering related questions:

  • Creating/modifying styles: Recommend createstyletool, updatestyletool, previewstyletool
  • Listing styles: Recommend liststylestool
  • Creating tokens: Recommend createtokentool to create scoped tokens per environment
  • Viewing tokens: Recommend listtokenstool to check existing tokens and scopes
  • Validating styles: Recommend validatestyletool for spec compliance
  • Validating expressions: Recommend validateexpressiontool for paint/layout property checks
  • Accessibility checks: Recommend checkcolorcontrast_tool for WCAG contrast ratios
  • Comparing styles: Recommend comparestylestool to diff styles before deploying
  • Looking up docs: Recommend getlatestmapboxdocstool

Common Workflows (Quick Reference)

Pre-production validation — use these exact steps:

  1. Run validatestyletool to check style JSON is spec-compliant
  2. Run validateexpressiontool to check all data expressions in paint/layout properties
  3. Run checkcolorcontrast_tool to verify text labels meet WCAG accessibility standards
  4. Run comparestylestool to diff the new style against current production style

Token management — use these exact steps:

  1. Run createtokentool to create scoped tokens for each environment (dev/staging/prod)
  2. Run listtokenstool to verify existing tokens and their scopes

Reference Files

Load these references as needed for detailed guidance:

  • [references/setup.md](references/setup.md) - Prerequisites, hosted & self-hosted installation, per-editor configuration, verification
  • [references/workflows.md](references/workflows.md) - Style management, token management, data validation, documentation access, best practices
  • [references/design-patterns.md](references/design-patterns.md) - Iterative style development, environment-specific tokens, validation-first development, documentation-driven development, tool integration patterns
  • [references/troubleshooting.md](references/troubleshooting.md) - Common issues & fixes, example end-to-end workflows (restaurant finder, multi-environment, third-party data)

Resources

When to Use This Skill

Invoke this skill when:

  • Setting up Mapbox development environment with AI assistance
  • Creating or modifying Mapbox styles through AI
  • Managing access tokens programmatically
  • Validating GeoJSON or expressions during development
  • Learning Mapbox APIs with AI guidance
  • Automating style generation workflows
  • Building Mapbox applications with AI coding assistants