About Muse Marketplace
Muse Marketplace is a registry and marketplace for sharing Muse avatars, personas, voices, and bundles. Its CLI, browsable static site, and safety checks support both publishing assets and installing verified listings.
Key features
- 01Browse and search asset listings
- 02Manage avatars, personas, voices, and bundles
- 03Validate files and SHA-256 checksums
- 04Install assets with integrity checks
- 05Browse animated avatar modes on site
Use cases
- 01Find Muse assets by name or tag
- 02Install a verified avatar or bundle
- 03Create and validate a new listing
MCP support
The same CLI binary can run as an MCP server. It exposes tools to search, list, show, validate, and install marketplace listings.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @reneturcios/muse-marketplaceLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| query | string | Yes | Search query matched against slug, name, description, tags, and author. |
Details
From the project READMEMuse Marketplace
The open marketplace & registry for shareable Muse assets.
Muse users will soon be able to share Muse Avatars with each other — an avatar sharing pop-up, animated previews of avatar "modes" like Working, the works. But sharing needs somewhere to live: an open registry where anyone can publish an avatar, persona, voice, or bundle, where every file carries a checksum, and where "safe" means actually checked, not just claimed.
That is this repo. We are building the Muse Avatar marketplace — starting now, in the open.
npx @reneturcios/muse-marketplace list
npx @reneturcios/muse-marketplace search tree
npx @reneturcios/muse-marketplace show jolly
npx @reneturcios/muse-marketplace install jolly
npx @reneturcios/muse-marketplace doctor
Or browse it as a site: open site/index.html (or the GitHub Pages deploy) — a dark, searchable grid with an animated mode switcher on every avatar.
What's inside
registry/— The registry itself. Every listing is a folderregistry/<kind>s/<slug>/with alisting.json+ its asset files. Kinds:avatar(primary),persona,voice,bundle.registry/index.jsonis generated from the listings (muse-marketplace index), never hand-edited; CI fails on drift.- Launch catalog (9 listings, all original, all installable) — 6 avatars: Jolly (the friendly green companion), Tree (a forest spirit), Straw Hat Explorer, Neon Founder, Cozy Scholar, Pixel Sprite — each with an original animated SVG per mode (idle / working / thinking / celebrating, plus extras like making, dance, milestone, error). 2 personas: Sharp Operator, Warm Companion. 1 bundle: Starter Pack (everything).
- CLI + MCP in one bin —
muse-marketplace(aliasmmkt) for humans; the same binary is an MCP server (muse-marketplace mcp) exposingmarketplace_search,marketplace_list,marketplace_show,marketplace_validate,marketplace_install. site/— A zero-build static marketplace: search, filter by kind + tag, click a card for the animated mode switcher and a copyable install command.docs/— SPEC (the listing schema), PUBLISHING (submit via PR), VETTING (the safety model), MODES, ARCHITECTURE, ROADMAP.
Quickstart
npm install
npm run build
npm test
node dist/cli.js list
node dist/cli.js install jolly --dest ./muse-assets # copies files, verifies sha256 before AND after, writes install-receipt.json
node dist/cli.js init my-avatar --kind avatar # scaffold a listing of your own
node dist/cli.js validate my-avatar
node dist/cli.js index # rebuild registry/index.json
node dist/cli.js doctor # registry health
Publish a listing
muse-marketplace init <your-slug> --kind avatar- Replace the placeholder SVGs /
persona.mdwith your real assets. - Run
muse-marketplace validate <your-slug>until clean, thenmuse-marketplace index. - Open a PR. Full walkthrough: docs/PUBLISHING.md.
The vetting / safety model (short version)
Nothing gets to call itself safe here without receipts — the same rule we run across the fleet: anything listed as safe must be validated with real checks.
- No executables, ever. Only allowlisted media types (SVG/PNG/JPEG/GIF/WebP, markdown, plain text, JSON, audio). Validation rejects executable extensions outright.
- Checksums on everything. Every file in every listing records its sha256 + byte size.
validaterecomputes them;installverifies before and after copying and refuses tampered listings. - Path safety. Absolute paths and
..traversal entries are rejected; installs stay inside the destination you name. - Vetted is earned.
safety.vettedflips totrueonly after the VETTING.md checklist is run by a reviewer — not by the author checking their own box. - Personas are plain markdown you can read in full before using — the file is the payload, nothing hidden.
Full model: docs/VETTING.md · Security reports: SECURITY.md
MCP usage
{ "mcpServers": { "muse-marketplace": { "command": "npx", "args": ["-y", "@reneturcios/muse-marketplace", "mcp"] } } }
Tools: marketplace_search · marketplace_list · marketplace_show · marketplace_validate · marketplace_install (install is confined to a caller-provided destination under the current working directory).
Roadmap
Ratings & reviews, signed listings, voice previews in the site player, a publish command that opens the PR for you, federation with other registries, and first-class wiring for Muse's native avatar sharing when it lands. Detail: docs/ROADMAP.md.
MIT. By Rene Turcios / CloudCorpRecords. Fleet: https://github.com/CloudCorpRecords
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.