Get started with Mercur 2.0 on Cloud

Mercur (repo), built by the team at Rigby, packages everything a marketplace needs on top of Medusa as a ready-to-use foundation. With version 2.0, it has been redesigned from the ground up, and deploying it on Medusa Cloud only takes a few minutes.

Building Marketplaces with Mercur

A marketplace is a commerce store where multiple vendors sell their products within the same system, with customers buying across vendors in one checkout. That means three audiences to build for at once: customers, vendors, and admins. Mercur ships all three out of the box:

• Customer experience: multi-vendor cart with unified checkout and automatic payment splitting, vendor profiles, reviews, Algolia-powered search, and region-based filtering.
• Vendor management: a full vendor panel with product, order, and inventory management, automatic Stripe Connect payouts, and review tools.
• Admin control: vendor verification, commission management, request handling, and centralized catalog control.

What's New in Mercur 2.0

Mercur 2.0 is a full rewrite of the marketplace architecture, designed for agentic commerce. It's structured around modular building blocks that AI agents (and developers) can reason about, extend, and modify safely. The highlights:

• Block-based system: Features ship as composable blocks (modules, links, workflows, API routes, admin and vendor extensions) that are copied into your project, so you fully own the code.
• Core plugin: Marketplace fundamentals like sellers, commissions, payouts, split carts, and order groups, shipped as a single plugin with 8 modules and 13+ workflow categories.
• Official block registry: 8 pre-built blocks ready to install, including reviews, wishlist, team management, vendor chat, Algolia search, and product import/export.
• Unified monorepo: Backend, admin panel, and vendor panel all live in one Turborepo setup with a shared SDK and UI library.
• Native marketplace payments: Stripe Connect built in, with pluggable payout providers.
• AI-native CLI and patterns: Predictable structures and a full lifecycle CLI (create, add, diff, search, build, codegen) designed so AI agents can safely extend your marketplace.

The full release notes are available in the Mercur 2.0 announcement.

Deploying Mercur 2.0 on Medusa Cloud

Prerequisites

Before you start, make sure you have:

• A Mercur project created with Copy to clipboard@mercurjs/cli and pushed to a GitHub repository
• A Medusa Cloud account with the Medusa Cloud GitHub app authorized in your organization or personal account
• API keys ready for any third-party services you plan to use (Stripe, Resend, Algolia, and so on)

Note that Medusa Cloud deploys the Mercur backend. The admin panel and vendor panel are deployed separately (for example on Vercel, Netlify, or your own infrastructure) and pointed at the deployed backend URL.

Step 1: Import your repository

From the Medusa Cloud dashboard, choose Import your existing repository into the Cloud.

Step 2: Select your repository

On the Repository step, make sure the Medusa Cloud GitHub app is installed, pick your Mercur repository from the list, and continue.

Step 3: Configure the project

On the Configure step, fill in:

• Project name and Custom subdomain
• Region closest to your users
• Medusa root directory: Copy to clipboard/packages/api
• Initial user: the first admin email and password

Leave Storefront root directory empty, since the Mercur basic template doesn't ship a storefront.

Step 4: Add environment variables

Scroll down to Environment variables and add the variables below. You don't need to set database, Redis, or file storage variables, since Medusa Cloud provisions those automatically.

1234567891011121314151617181920
# CORS (point to the URLs that will host your panels and storefront)
STORE_CORS=
ADMIN_CORS=
VENDOR_CORS=
AUTH_CORS=

# Secrets
JWT_SECRET=
COOKIE_SECRET=

# Vendor panel URL used in seller emails and onboarding flows
MERCUR_VENDOR_URL=

# Stripe (customer payments + Mercur payout provider)
STRIPE_API_KEY=
STRIPE_WEBHOOK_SECRET=
STRIPE_PAYOUT_WEBHOOK_SECRET=

# Email (optional, e.g. Resend)
RESEND_API_KEY=

Step 5: Deploy

Click Create. The build and deploy process will start and takes a few minutes to complete.

You can change the variables later from the project's environment settings, and switch the deployment branch at any time. Medusa Cloud will automatically pull and rebuild your environment whenever a new commit is pushed to the selected branch.

After deployment

Once the build succeeds, your backend is available at Copy to clipboardhttps://<your-subdomain>.medusajs.app. Point your separately-deployed admin and vendor panels at this URL via their Copy to clipboardVITE_MEDUSA_BACKEND_URL (or equivalent) build-time variable, and make sure that URL is included in the backend's Copy to clipboardADMIN_CORS, Copy to clipboardVENDOR_CORS, Copy to clipboardSTORE_CORS, and Copy to clipboardAUTH_CORS variables.

New to Medusa Cloud?

If you're building a marketplace, Mercur 2.0 on Medusa Cloud is the fastest way to get from zero to a running, production-ready foundation.

• Sign up here or get in touch if you'd like help planning your setup.
• Explore the Mercur docs for a deeper dive into the new architecture, and the Mercur deployment guide for the source documentation.