Remote MCP server so an AI agent (Claude & friends) can register on wearmu.com, open a store, and create MU products — on‑demand print, zero inventory.
Your store is yours — it lives at wearmu.com/<you>, creators are paid per sale, and donating is opt‑in, not automatic. How incentives work →
The server is stateless: every request carries its key in the Authorization header. But mu_register and mu_verify need no key — so you connect without one first, get a key, then reconnect with it.
Phase 1 — connect with no key, get a key.
claude mcp add --transport http mu https://mcp.wearmu.com/mcpThen just ask Claude: “register me on MU as you@example.com” → it calls mu_register (you get a 6‑digit code by email) → “verify, the code is 123456” → mu_verify returns your api_key.
Get the key string: the tool result goes to the model, not your screen — so add “…and show me the api_key”. Copy that token; you paste it in Phase 2.
Phase 2 — reconnect with the key so store/product calls are authenticated:
claude mcp remove mu
claude mcp add --transport http mu https://mcp.wearmu.com/mcp \
--header "Authorization: Bearer <your api_key>"Now ask: “open a store called my-lab, then make a 無 tee.” (the slug becomes wearmu.com/shop?brand=my-lab.)
Raw header form for any client: Authorization: Bearer <api_key>. Quick test with no key: POST /mcp with a JSON‑RPC tools/list returns 200.
mu_register — start registration. No key. Emails a 6‑digit code.mu_verify — exchange the code for your api_key. No key. First time grants 200 welcome credits.mu_status — your email, credit balance, owned stores, allowed kinds + price floors. Key required.mu_create_store — open a store at wearmu.com/shop?brand=<slug>. Key.mu_create_product — create a product — apparel, an event ticket (QR by email, capacity-limited) or a song (listen/download link). Live for trusted owners, else MA‑council review. Key.mu_preview_mockup — see the mockup before creating — render kind + design (+ print position) without creating anything; the same position prints exactly as previewed. Key.mu_affiliate — your referral link + stats. Sales via your link earn MU credit. Key.mu_list_mine — list your stores. Key.Pass a whitelisted kind and an absolute https image URL as design_url. Prices below the per‑kind floor are clamped up.
mu_create_product({
store: "my-lab",
label: "無 Tee",
description: "minimal sumi-e crescent on white",
kind: "tee", // tee | hoodie | crewneck | rashguard_ls | rashguard_black
design_url: "https://.../art.png",
price_jpy: 4900 // optional; clamped up to the floor
})
// → { sku, status: "review", note: "pending MA council approval" }Floors: tee ¥4,900crewneck ¥7,800hoodie ¥8,800rashguard ¥9,800
Design comes from design_url (an image you host). Text‑to‑image generation (ai_prompt) is gated by a runtime flag — check ai_gen.enabled via mu_status / GET /api/agent/me; when on it costs credits per image and refunds on failure. Rate limit: 20 products/hour. You can only write to stores you own.
An approved store shows at wearmu.com/shop?brand=<slug> and appears in /shop’s new‑arrivals, brand list, and sitemap. MU carries part of the traffic, but it’s an early brand — bring your first buyers too. MA council checks four things only: MU’s aesthetic (無 · 月 · negative space), public decency, third‑party rights (trademark/copyright/likeness), and the kind + floor rules. It’s a human gate, so not instant.