Skills ZICQ category：Documents mapbox-mcp-devkit-patterns

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.

1303 installs

Official URL：skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

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

When to use it

MCP DevKit

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Mapbox MCP DevKit Patterns; What is Mapbox MCP DevKit?; When to Use MCP DevKit; Use DevKit when:; Don't use DevKit for:; Key Tools. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references references/setup.md, references/workflows.md, references/design-patterns.md, references/troubleshooting.md. Those resources load on demand.

Mapbox MCP DevKit PatternsWhat is Mapbox MCP DevKit?When to Use MCP DevKitUse DevKit when:Don't use DevKit for:Key ToolsCommon Workflows (Quick Reference)Reference FilesResourcesWhen to Use This Skill

Source category：skills.sh agent-skill

Sources & links

Market sources：skills.sh

Full package on GitHub

OSS Skill ranking

SKILL.md & Agent activation

Official spec ↗

name: mapbox-mcp-devkit-patterns
description: 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.

DiscoverThe client exposes names and descriptions to the agent.
ActivateYour request or the task context selects the skill and loads its instructions.
Load resourcesReferenced scripts, documentation and assets are used when needed.

Files referenced by the instructions · 4

references/setup.md
references/workflows.md
references/design-patterns.md
references/troubleshooting.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "mapbox-mcp-devkit-patterns" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-22964b92cc5b3c31-Mapbox-Mcp-Devkit-Patterns.html
Save it as .cursor/skills/mapbox-mcp-devkit-patterns/SKILL.md or .claude/skills/mapbox-mcp-devkit-patterns/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/mapbox/mapbox-agent-skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/mapbox/mapbox-agent-skills' --list

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

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

SKILL.md source Copy freely; the source file is unchanged

---
name: mapbox-mcp-devkit-patterns
description: 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.
---

# 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](https://github.com/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](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

- [Mapbox MCP DevKit Server](https://github.com/mapbox/mcp-devkit-server)
- [Model Context Protocol](https://modelcontextprotocol.io)
- [Mapbox Style Specification](https://docs.mapbox.com/style-spec/)
- [Mapbox API Documentation](https://docs.mapbox.com/api/)
- [Token Scopes Reference](https://docs.mapbox.com/api/accounts/tokens/)

## 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

Readable layout

name: mapbox-mcp-devkit-patterns description: 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.

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:

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

Token management — use these exact steps:

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

Reference Files