Muse Marketplace

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026

Open marketplace and registry for shareable Muse assets: avatars, personas, voices, and bundles.

The publisher's own server: muse.space

VerifiedSTDIODesktop onlyFiles & StorageAI & ML

Overview

AI-generated overview

MCP server for the Muse Marketplace registry: lets an assistant search, inspect, validate and install shareable Muse avatars, personas, voices and bundles.

What you can do
  • Search and list marketplace listings by name, tag, slug, author, kind or description
  • Show the full listing record for a single slug
  • Validate a listing: schema, file existence, sha256 checksums, allowed media types and path safety
  • Install a listing into a destination directory under the current working directory, verifying checksums before and after copying
When to use it
Useful when you want an assistant to find and pull Muse avatar, persona, voice or bundle assets from the open registry into a local project, and to check that a listing is intact and free of executables before using it.
Requirements
Runs locally over stdio, either via npx with the npm package or via the Docker image. No authentication, environment variables or headers are declared. The install tool writes files into a destination directory under the current working directory.
Before you install
Install writes files to disk, so point it at a destination you intend to use. Safety depends on the registry's checks: listings are only marked vetted after a reviewer runs the checklist, and install refuses tampered listings, but unvetted listings should be treated with care. Personas are markdown payloads that an assistant may read and act on.

Installation

In SourceWeft

  1. Open Muse Marketplace in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Muse 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.

bash
npx @reneturcios/muse-marketplace listnpx @reneturcios/muse-marketplace search treenpx @reneturcios/muse-marketplace show jollynpx @reneturcios/muse-marketplace install jollynpx @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 folder registry/<kind>s/<slug>/ with a listing.json + its asset files. Kinds: avatar (primary), persona, voice, bundle. registry/index.json is 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 (alias mmkt) for humans; the same binary is an MCP server (muse-marketplace mcp) exposing marketplace_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

bash
npm installnpm run buildnpm test
node dist/cli.js listnode dist/cli.js install jolly --dest ./muse-assets   # copies files, verifies sha256 before AND after, writes install-receipt.jsonnode dist/cli.js init my-avatar --kind avatar          # scaffold a listing of your ownnode dist/cli.js validate my-avatarnode dist/cli.js index                                  # rebuild registry/index.jsonnode dist/cli.js doctor                                 # registry health

Publish a listing

  1. muse-marketplace init <your-slug> --kind avatar
  2. Replace the placeholder SVGs / persona.md with your real assets.
  3. Run muse-marketplace validate <your-slug> until clean, then muse-marketplace index.
  4. 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. validate recomputes them; install verifies 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.vetted flips to true only 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

json
{ "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

Source: README.md at commit 6f42cfd

Tools

5

marketplace_list

List Muse Marketplace listings, optionally filtered by kind or tag.

Parameterstagkind

marketplace_show

Show the full listing record for one slug.

Parametersslugrequired

marketplace_validate

Validate a listing: schema, file existence, sha256 checksums, allowed media types, and path safety.

Parametersslugrequired

marketplace_install

Install a listing into a destination directory under the current working directory. Verifies checksums before and after copy and refuses tampered listings.

Parametersdestslugrequired

Version history

1
  1. v0.1.0LatestOct 30, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Muse integrations