Skip to content

Commit 39a8e17

Browse files
[docs] Add MCP Registry submission and positioning documentation
Comprehensive documentation for submitting to the official MCP Registry and positioning the Mapbox DevKit MCP Server in the market. Changes: - Updated server.json description to better differentiate from main Mapbox MCP server - Emphasizes developer toolkit focus (not geospatial API features) New Documentation: 1. REGISTRY_SUBMISSION.md - Complete submission process with mcp-publisher tool - Prerequisites, authentication, publishing steps - Troubleshooting common issues - Update workflow for new versions 2. REGISTRY_SUBMISSION_CHECKLIST.md - Actionable checklist for actual submission - Pre/post-submission tasks - Marketing asset templates (badges, social media copy) - Success metrics to track - Platform-specific instructions (HN, Twitter, LinkedIn) 3. POSITIONING.md - Comparison table: Mapbox MCP Server vs DevKit MCP Server - Unique value proposition and differentiators - Target audience messaging (frontend devs, full-stack, AI/ML engineers) - Use case examples with before/after comparisons - Content marketing ideas (blog posts, videos, social media) - Partnership opportunities (AI platforms, dev tools, education) - Launch strategy with 4-phase rollout plan 4. BLOG_POST_DRAFT.md - Complete blog post ready for publication - Real-world use case examples - Technical highlights and capabilities - Getting started guide with code examples - Comparison with main Mapbox MCP server - Call to action and community links Key Positioning: - "AI-powered development toolkit for building Mapbox applications" - Complements main Mapbox MCP Server (geospatial features) - Focus: Style creation, validation, accessibility, security, cartography - Differentiators: Quality validation, educational skills, workflow automation Target Audiences: - Frontend developers building map UIs - Full-stack developers needing security best practices - AI/ML engineers adding maps to applications - Technical product managers prototyping features Next Steps: 1. Run: mcp-publisher login github 2. Run: mcp-publisher publish 3. Execute post-submission checklist for awareness Related: - MCP Registry: https://registry.modelcontextprotocol.io - Main Mapbox MCP Server: https://github.com/mapbox/mcp-server Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
1 parent ea796dd commit 39a8e17

File tree

5 files changed

+1137
-1
lines changed

5 files changed

+1137
-1
lines changed

docs/BLOG_POST_DRAFT.md

Lines changed: 338 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,338 @@
1+
# Introducing the Mapbox DevKit MCP Server: AI-Powered Map Development
2+
3+
_Draft blog post for announcing the Mapbox DevKit MCP Server_
4+
5+
---
6+
7+
Building map applications has traditionally required deep expertise in cartography, style specifications, token management, and accessibility standards. Today, we're excited to introduce the **Mapbox DevKit MCP Server**—bringing AI assistance to the entire map development workflow.
8+
9+
## What is the Mapbox DevKit MCP Server?
10+
11+
The Mapbox DevKit MCP Server is a [Model Context Protocol](https://modelcontextprotocol.io) server that transforms AI assistants like Claude into expert Mapbox development partners. Through natural language conversations, developers can create custom map styles, validate production readiness, manage access tokens securely, and learn cartography best practices.
12+
13+
It's part of Mapbox's commitment to making map development more accessible while maintaining professional quality and security standards.
14+
15+
## Key Capabilities
16+
17+
### 🎨 AI-Powered Style Creation
18+
19+
Create custom map styles through natural conversation:
20+
21+
```
22+
You: "Create a dark cyberpunk map style emphasizing nightlife venues"
23+
24+
Claude: I'll create a dark-themed map style with neon colors perfect for nightlife.
25+
[Creates style with vibrant magentas, cyans, and purples on dark backgrounds]
26+
27+
✅ Style created: mapbox://styles/username/ckl3d2m4p0001
28+
🔗 Preview: https://api.mapbox.com/styles/v1/...
29+
✅ Validation: Production-ready (all checks passed)
30+
```
31+
32+
The style builder understands themes like "nature-focused," "minimal monochrome," or "retro 80s neon" and automatically generates appropriate color schemes, layer styling, and typography.
33+
34+
### ✅ Production-Ready Validation
35+
36+
Before deploying to production, validate your styles automatically:
37+
38+
- **Expression validation**: Catch syntax errors in filters, paint properties, and layout expressions
39+
- **Accessibility checks**: WCAG 2.1 compliance for color contrast (AA/AAA levels)
40+
- **GeoJSON validation**: Verify coordinate ranges, polygon ring closure, and data structure
41+
- **Performance optimization**: Identify unused sources, duplicate layers, and simplifiable expressions
42+
- **Style comparison**: Understand what changed between versions
43+
44+
All validation runs **offline** (no API calls) and completes in milliseconds.
45+
46+
### 🔐 Secure Token Management
47+
48+
Set up access tokens with proper security from day one:
49+
50+
```
51+
You: "Set up tokens for my restaurant finder app at restaurantfinder.com"
52+
53+
Claude: I'll create a secure token setup for your project.
54+
55+
✅ Development Token (pk.ey...)
56+
- Restricted to: http://localhost:*
57+
- Scopes: styles:read, styles:list
58+
59+
✅ Production Token (pk.ey...)
60+
- Restricted to: https://restaurantfinder.com
61+
- Scopes: styles:read
62+
63+
✅ Backend Secret Token (sk.ey...)
64+
- Server-side only (never expose in client code)
65+
- Scopes: styles:write, styles:read
66+
67+
🎯 Initial style created and validated
68+
🔗 Preview: [URL]
69+
```
70+
71+
The server ensures:
72+
73+
- URL restrictions are set correctly
74+
- Public tokens never get secret scopes
75+
- Backend tokens are never suggested for client-side use
76+
- Token scope matches your actual needs
77+
78+
### 🎓 Built-in Cartography Expertise
79+
80+
Learn best practices through 5 specialized **agent skills**:
81+
82+
- **mapbox-cartography**: Color theory, visual hierarchy, typography principles
83+
- **mapbox-token-security**: Scope management, rotation strategies, security patterns
84+
- **mapbox-style-patterns**: Common layer configurations for typical use cases
85+
- **mapbox-integration-patterns**: Framework-specific integration (React, Vue, Svelte, Angular)
86+
- **mapbox-style-quality**: Validation workflows, accessibility, optimization strategies
87+
88+
These skills teach AI assistants (and you!) professional map development practices.
89+
90+
### 🚀 Workflow Automation
91+
92+
Seven orchestrated prompts handle common development tasks:
93+
94+
1. **create-and-preview-style**: Create a style and generate shareable preview link
95+
2. **build-custom-map**: Use AI to build themed map styles
96+
3. **design-data-driven-style**: Create maps with dynamic, data-driven properties
97+
4. **setup-mapbox-project**: Complete project setup with proper token security
98+
5. **debug-mapbox-integration**: Systematic troubleshooting for integration issues
99+
6. **analyze-geojson**: Validate and visualize GeoJSON data
100+
7. **prepare-style-for-production**: Comprehensive quality validation workflow
101+
102+
Each prompt chains multiple tools together with best practices built-in.
103+
104+
## Real-World Use Cases
105+
106+
### Rapid Prototyping
107+
108+
Product manager: "Can we see what a dark mode map would look like for our nightlife app?"
109+
110+
With DevKit: **5 minutes** to fully styled, validated preview
111+
Without DevKit: **2-4 hours** of manual styling and iteration
112+
113+
### Quality Assurance
114+
115+
Developer: "Is this style ready for production?"
116+
117+
With DevKit: **Automatic validation** catches expression errors, accessibility issues, optimization opportunities
118+
Without DevKit: **Runtime errors**, failed accessibility audits, unoptimized performance
119+
120+
### Security Setup
121+
122+
New project: "We need to set up Mapbox tokens securely"
123+
124+
With DevKit: **Guided setup** with proper restrictions, scopes, and validation
125+
Without DevKit: **Common mistakes** like missing URL restrictions, wrong scopes, exposed secrets
126+
127+
## How It Works
128+
129+
The Mapbox DevKit MCP Server uses the [Model Context Protocol](https://modelcontextprotocol.io)—an open standard for connecting AI assistants to external tools and data sources.
130+
131+
**For developers**: Install via npm and configure in your AI client (Claude Desktop, VS Code, Cursor):
132+
133+
```bash
134+
npm install -g @mapbox/mcp-devkit-server
135+
```
136+
137+
**For AI assistants**: Access 25+ tools, 7 prompts, 4 resources, and 5 skills through natural conversation.
138+
139+
## What Makes It Different?
140+
141+
### vs. Main Mapbox MCP Server
142+
143+
Mapbox now offers **two complementary MCP servers**:
144+
145+
| Capability | Mapbox MCP Server | Mapbox DevKit MCP Server |
146+
| ------------ | ------------------------------ | -------------------------------------- |
147+
| **Purpose** | Geospatial intelligence | Map development toolkit |
148+
| **Use Case** | Apps need location features | Building map applications |
149+
| **Features** | Geocoding, routing, POI search | Style creation, validation, token mgmt |
150+
| **Target** | AI agents, chatbots | Developers building maps |
151+
152+
Use the main server when your **app needs geospatial features**. Use DevKit when you're **building the map itself**.
153+
154+
### vs. Manual Development
155+
156+
- ⏱️ **10x faster prototyping** through natural language
157+
-**Better quality** through automatic validation
158+
- 📚 **Educational** with built-in best practices
159+
- 🔄 **Iterative** development through conversation
160+
161+
## Getting Started
162+
163+
### Installation
164+
165+
**npm (recommended):**
166+
167+
```bash
168+
npm install -g @mapbox/mcp-devkit-server
169+
```
170+
171+
**npx (no installation):**
172+
173+
```bash
174+
npx @mapbox/mcp-devkit-server
175+
```
176+
177+
### Configuration
178+
179+
Add to your MCP client (Claude Desktop example):
180+
181+
```json
182+
{
183+
"mcpServers": {
184+
"mapbox-devkit": {
185+
"command": "npx",
186+
"args": ["-y", "@mapbox/mcp-devkit-server"],
187+
"env": {
188+
"MAPBOX_ACCESS_TOKEN": "your_token_here"
189+
}
190+
}
191+
}
192+
}
193+
```
194+
195+
### First Map
196+
197+
Open your AI assistant and try:
198+
199+
```
200+
"Create a nature-focused map style emphasizing parks and green spaces,
201+
centered on Central Park in New York"
202+
```
203+
204+
The AI will:
205+
206+
1. Create a custom style with earth tones and emphasized parks
207+
2. Generate a preview URL
208+
3. Validate for production readiness
209+
4. Report any accessibility or quality issues
210+
211+
## Technical Highlights
212+
213+
### Comprehensive Tool Suite
214+
215+
**25+ tools** organized by category:
216+
217+
- **Style Management**: Create, update, retrieve, delete, preview styles
218+
- **Token Management**: Create, list tokens with proper scopes
219+
- **Validation**: Expression validation, GeoJSON validation, accessibility checks
220+
- **Optimization**: Style optimization, comparison, performance analysis
221+
- **Utilities**: Coordinate conversion, bounding boxes, geocoding
222+
- **Documentation**: Reference materials, field definitions, best practices
223+
224+
### Offline-First Design
225+
226+
Many operations run entirely offline:
227+
228+
- Style validation (expressions, GeoJSON)
229+
- Accessibility checking (WCAG contrast ratios)
230+
- Style optimization (redundancy removal)
231+
- Style comparison (diff analysis)
232+
233+
No API calls = fast, free, private.
234+
235+
### Quality by Default
236+
237+
All style-creation workflows **automatically validate** before presenting results:
238+
239+
- Expression syntax checking
240+
- WCAG AA accessibility compliance
241+
- Optimization opportunities
242+
- Deployment readiness assessment
243+
244+
Warnings are informational—users can ignore them for prototypes but have visibility into production readiness.
245+
246+
### Enterprise-Ready
247+
248+
- **Distributed tracing**: OpenTelemetry integration for observability
249+
- **Configurable**: Environment variables for feature toggles
250+
- **Tested**: 386 test cases with comprehensive coverage
251+
- **Documented**: Extensive documentation and examples
252+
- **Type-safe**: Full TypeScript implementation with Zod validation
253+
254+
## What's Next?
255+
256+
We're continuously improving the Mapbox DevKit MCP Server based on developer feedback. Upcoming features include:
257+
258+
- **Tileset integration**: Validate and preview custom tilesets
259+
- **Batch operations**: Style migration and bulk updates
260+
- **Advanced analytics**: Usage insights and optimization recommendations
261+
- **Team workflows**: Shared styles and collaborative development
262+
- **Framework templates**: Quick-start projects for React, Vue, Svelte
263+
264+
## Learn More
265+
266+
- **GitHub**: [github.com/mapbox/mcp-devkit-server](https://github.com/mapbox/mcp-devkit-server)
267+
- **npm**: [@mapbox/mcp-devkit-server](https://www.npmjs.com/package/@mapbox/mcp-devkit-server)
268+
- **MCP Registry**: [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io)
269+
- **Documentation**: [Full API reference and guides](https://github.com/mapbox/mcp-devkit-server#readme)
270+
271+
## Join the Community
272+
273+
We'd love to hear how you're using the Mapbox DevKit MCP Server:
274+
275+
- **Share** your maps on Twitter/X with [#MapboxDevKit](https://twitter.com/hashtag/MapboxDevKit)
276+
- **Report issues** or request features on [GitHub](https://github.com/mapbox/mcp-devkit-server/issues)
277+
- **Contribute** improvements via pull requests
278+
- **Connect** with other developers on [Mapbox Community Forum](https://community.mapbox.com)
279+
280+
---
281+
282+
_The Mapbox DevKit MCP Server is open source (MIT License) and available today. Get started at [github.com/mapbox/mcp-devkit-server](https://github.com/mapbox/mcp-devkit-server)._
283+
284+
---
285+
286+
## Quotes (to be filled in)
287+
288+
> "Quote from Mapbox leadership about AI-powered development tools"
289+
> [Name], [Title], Mapbox
290+
291+
> "Quote from developer who used the tool during beta"
292+
> [Name], [Company/Title]
293+
294+
> "Quote about MCP ecosystem"
295+
> [Name], Anthropic or MCP community
296+
297+
---
298+
299+
## Technical Details (Appendix)
300+
301+
### System Requirements
302+
303+
- Node.js 22+
304+
- Mapbox access token
305+
- MCP-compatible client (Claude Desktop, VS Code, Cursor, etc.)
306+
307+
### Supported Platforms
308+
309+
- macOS (Intel and Apple Silicon)
310+
- Linux (all major distributions)
311+
- Windows 10/11
312+
- Docker (cross-platform)
313+
314+
### Integration Options
315+
316+
- **CLI**: Direct command-line usage
317+
- **MCP Clients**: Claude Desktop, VS Code, Cursor
318+
- **Programmatic**: Import as Node.js package
319+
- **Docker**: Containerized deployment
320+
321+
### Security & Privacy
322+
323+
- All API calls use HTTPS
324+
- Access tokens stored securely in environment variables
325+
- Offline tools process data locally
326+
- No telemetry without explicit opt-in (OpenTelemetry)
327+
- Open source for transparency
328+
329+
---
330+
331+
**Media Contact**: [Contact information]
332+
333+
**Assets Available**:
334+
335+
- Screenshots of tool in action
336+
- Demo video (5 minutes)
337+
- Architecture diagrams
338+
- Logo/branding assets

0 commit comments

Comments
 (0)