[Initiative] Mercur CLI & Registry Workflow #694
Description
Summary
To support the new modular Mercur architecture, we are introducing a Mercur CLI and a registry-based workflow for managing marketplace functionality.
The CLI will be the primary interface for working with Mercur and composing marketplaces from reusable blocks.
Motivation
As Mercur moves toward a block-based architecture, developers need a clear and predictable way to:
- discover available functionality
- add it to a project
- customize it safely
- keep track of local changes over time
Without dedicated tooling, customization becomes implicit, hard to reason about, and difficult to maintain.
This initiative focuses on making marketplace composition explicit and developer-owned.
Scope
This initiative introduces a CLI-driven workflow that allows developers to:
- initialize Mercur in new or existing Medusa projects
- discover blocks from one or more registries
- install and update blocks
- compare local customizations with upstream registry versions
- list, search, and inspect available blocks
- create and build registries for internal or public use
The workflow is inspired by tools like shadcn/ui and is designed to avoid hidden code generation or implicit behavior.
Impact
- Developers retain full ownership of their marketplace code
- Customization becomes explicit, transparent, and easy to reason about
- Upgrades and experimentation remain safe and manageable
This initiative is a key part of making Mercur flexible without introducing magic or lock-in.
Relationship to the Roadmap
This initiative is tracked on the public Mercur roadmap.
Current status: In Progress
Feedback & Discussion
This issue is intended for high-level discussion and feedback around the CLI and registry workflow.
Implementation details and task-level work are tracked internally and are intentionally out of scope for this issue.