Roadmap
MyClaude roadmap: what's live, what's next, and where the platform is headed.
MyClaude supports 9 product categories with Stripe Connect payouts, XP-based gamification, and a CLI-first publishing pipeline. This page covers what's live today and where the platform is headed.
What's live right now?
The marketplace core is production-ready. Everything below is shipped and working:
| Area | What's live |
|---|---|
| Marketplace | Browse, search, and install across 9 categories (skills, squads, agents, workflows, design-systems, prompts, claude-md, applications, systems) |
| CLI | myclaude install, myclaude publish, myclaude search via @myclaude-cli/cli |
| Payments | Stripe Connect Express with 92% creator / 8% platform split, webhook-driven order creation |
| Profiles | Public profiles at myclaude.sh/u/{username} with SSR and OpenGraph metadata |
| Product pages | SSR-rendered pages at myclaude.sh/p/{slug} with structured data |
| Gamification | XP system (8 actions), 8 ranks (Newcomer through Legend), 45 achievements across 9 categories |
| Security | Firebase Admin auth on all API routes, signed URLs for paid downloads, rate limiting, DOMPurify sanitization |
| Documentation | Fumadocs-powered docs site with GEO-optimized content |
What's coming next?
These features are in active development or planned for the near term.
| Feature | Status | What it does |
|---|---|---|
| Creator Engine | In development | Standalone tool for scaffolding, testing, and publishing products without touching the web UI |
| Advanced search | Planned | Faceted filtering by category, price range, rating, and download count |
| Notification system | Planned | In-app and email notifications for sales, reviews, followers, and achievement unlocks |
| Review system v2 | Planned | Verified purchase reviews with rating aggregation and creator responses |
Creator Engine is the highest-priority initiative. It turns product creation from a manual process into a guided, CLI-native workflow with built-in validation against the vault.yaml spec.
What's on the medium-term horizon?
These capabilities are being explored. No commitments on timing, but the architecture is designed to support them.
| Feature | Status | What it does |
|---|---|---|
| MCP server integration | Exploring | Native Model Context Protocol support so products can expose tools, resources, and prompts directly to Claude Code |
| Team and org accounts | Exploring | Shared billing, team-level publishing, and permission management for organizations |
| Plugin API | Exploring | Public API for third-party integrations, CI/CD hooks, and custom marketplace clients |
| i18n expansion | Planned | Full localization beyond EN/PT-BR/ES, with community-contributed translations |
| Versioning and changelogs | Exploring | Semantic versioning for products with automatic changelog generation and update notifications |
MCP integration is the most architecturally significant item here. It would let a single myclaude install add tools directly to your Claude Code session context without manual configuration.
What's the long-term vision?
Two directions the platform is evolving toward:
AI-native package manager. MyClaude is building toward becoming the package manager for AI-augmented development, the same way npm serves JavaScript. The CLI already handles install, publish, and search. The next steps are dependency resolution, version pinning, and lockfiles.
Decentralized marketplace protocol. Exploring a protocol layer that lets anyone run a compatible marketplace node, with shared product discovery and federated creator identity. This is early-stage thinking, not a commitment.
How do you influence the roadmap?
The roadmap is shaped by usage data and direct community input.
| Channel | What to use it for |
|---|---|
| GitHub Issues | Bug reports, feature requests with concrete use cases |
| Community discussions | Upvote existing proposals, share workflows that reveal missing capabilities |
| Product reviews | Signal which product categories need better tooling |
| Direct feedback | Contact via myclaude.sh for partnership or integration proposals |
Feature requests with real use cases attached move faster than abstract suggestions. If you're building something and hit a gap, that's the most valuable signal.
Related pages
- Concepts Overview -- how the marketplace works
- Architecture -- technical infrastructure
- Changelog -- what shipped and when