[docs] Add MCP Registry submission and positioning documentation #56
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Comprehensive documentation for submitting the Mapbox DevKit MCP Server to the official MCP Registry and positioning it effectively in the market.
This PR provides everything needed to:
Files Added
1. server.json (Updated)
2. docs/REGISTRY_SUBMISSION.md
Complete technical submission guide:
3. docs/REGISTRY_SUBMISSION_CHECKLIST.md ⭐ Action-Oriented
Ready-to-execute checklist:
4. docs/POSITIONING.md ⭐ Strategic Marketing
Complete positioning strategy:
5. docs/BLOG_POST_DRAFT.md ⭐ Publication-Ready
Complete announcement blog post:
Key Positioning Messages
What It Is
"AI-powered development toolkit for building Mapbox applications"
How It's Different
vs. Main Mapbox MCP Server:
Use main server when: Your app needs to find places or calculate routes
Use DevKit when: You're building the map application itself
Target Message
"Build production-ready maps with AI assistance—no cartography degree required"
Next Steps After Merge
Immediate (Day 1)
brew install mcp-publishermcp-publisher login githubmcp-publisher publishWeek 1
Week 2-4
Success Metrics to Track
Awareness:
Engagement:
Related
🤖 Generated with Claude Code