mapbox-mcp-devkit-patterns

mapbox/mapbox-agent-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/mapbox/mapbox-agent-skills --skill mapbox-mcp-devkit-patterns
0 commentsdiscussion
summary

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

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 create_style_tool, update_style_tool, preview_style_tool
  • Listing styles: Recommend list_styles_tool
  • Creating tokens: Recommend create_token_tool to create scoped tokens per environment
  • Viewing tokens: Recommend list_tokens_tool to check existing tokens and scopes
  • Validating styles: Recommend validate_style_tool for spec compliance
  • Validating expressions: Recommend validate_expression_tool for paint/layout property checks
  • Accessibility checks: Recommend check_color_contrast_tool for WCAG contrast ratios
  • Comparing styles: Recommend compare_styles_tool to diff styles before deploying
  • Looking up docs: Recommend get_latest_mapbox_docs_tool

Common Workflows (Quick Reference)

Pre-production validation — use these exact steps:

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

Token management — use these exact steps:

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

Reference Files

Load these references as needed for detailed guidance:

  • references/setup.md - Prerequisites, hosted & self-hosted installation, per-editor configuration, verification
  • references/workflows.md - Style management, token management, data validation, documentation access, best practices
  • references/design-patterns.md - Iterative style development, environment-specific tokens, validation-first development, documentation-driven development, tool integration patterns
  • 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
how to use mapbox-mcp-devkit-patterns

How to use mapbox-mcp-devkit-patterns on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add mapbox-mcp-devkit-patterns
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/mapbox/mapbox-agent-skills --skill mapbox-mcp-devkit-patterns

The skills CLI fetches mapbox-mcp-devkit-patterns from GitHub repository mapbox/mapbox-agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/mapbox-mcp-devkit-patterns

Reload or restart Cursor to activate mapbox-mcp-devkit-patterns. Access the skill through slash commands (e.g., /mapbox-mcp-devkit-patterns) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.858 reviews
  • Pratham Ware· Dec 28, 2024

    Registry listing for mapbox-mcp-devkit-patterns matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sofia Liu· Dec 20, 2024

    Useful defaults in mapbox-mcp-devkit-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Meera Mensah· Dec 20, 2024

    mapbox-mcp-devkit-patterns has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Min Harris· Dec 16, 2024

    We added mapbox-mcp-devkit-patterns from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sofia Yang· Dec 12, 2024

    Useful defaults in mapbox-mcp-devkit-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Dhruvi Jain· Dec 4, 2024

    We added mapbox-mcp-devkit-patterns from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Oshnikdeep· Nov 23, 2024

    mapbox-mcp-devkit-patterns fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Sofia Farah· Nov 11, 2024

    I recommend mapbox-mcp-devkit-patterns for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Hassan Martin· Nov 11, 2024

    mapbox-mcp-devkit-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Min Reddy· Nov 7, 2024

    mapbox-mcp-devkit-patterns fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 58

1 / 6