ShipWithMuse is a curated directory of what people are building with Meta Muse. The site describes itself as "a catalog of what people build with Muse," and its Product Hunt tagline is "Discover what people are building with Muse." Rather than publishing its own tutorials or demos, it collects real builds from around the web — agents, connectors, apps, games, skills, resources and local Glimmer runs — and presents them in one searchable catalog. Every entry is linked back to its original public source, whether that is an X post, a Reddit thread, a GitHub repository, a YouTube video, a blog resource or a website. It is built for developers, builders and curious observers who want to see the concrete things people have made with Muse rather than read abstract descriptions of the platform.
The problem ShipWithMuse addresses is dispersion. Builds made with Meta Muse appear in many different places: developers post screenshots and results on X, hobbyists share custom connectors on the r/MuseAgent subreddit, engineers publish repositories on GitHub, video creators walk through results on YouTube, and writers publish guides and benchmark analyses on their own blogs. Following all of those channels individually is impractical, and much of the work is easy to miss. ShipWithMuse aggregates that material into a single catalog of more than 1,000 builds — the homepage header reads "1079 usecases built now with Muse" — so that anyone evaluating the platform can see what is actually being shipped in practice rather than relying on marketing claims. Because the entries link to their sources, the directory doubles as an index of evidence: benchmarks, demos, repositories and how-to guides that can be checked firsthand.
Browsing is organised around build type and page. The catalog lists all 1,079 builds, then offers type filters with their own counts: X posts (462), Reddit posts (124), GitHub (143), Videos (61), Sites (33), Skills (110), Resources (137) and Guides (9). A separate "Star picks" toggle lets visitors show only the curated highlights. Results are paginated — the full catalog spans 27 pages — and each item is presented as a card carrying the creator's handle and avatar, a category label, a like count where one exists, and a direct link out to the original post, repository, video or site. Newly submitted builds are surfaced at the top of the homepage, alongside a prompt inviting visitors to submit their own work.
Entries span a wide range of categories, which is itself a picture of what Muse is being used for. Coding & dev tools covers items such as the Browserbase plugin for Muse Code, a guide to Muse Code CLI commands, and the Muse Code Uninstaller utility. Connectors & MCP includes a Linear connector built by Muse in under a minute, the muse-fileapi local file connector, and a developer's guide to building Muse connectors. Games & 3D features five self-playing games written one-shot with Muse Glimmer, a Three.js browser driving demo and a Mini Golf game ported to VR. Benchmarks & research collects tests such as 105 planted bugs pitting Muse Spark 1.3 against frontier models, Spark 1.3's first place on Website Arena, and a privacy teardown of the Muse apps.
Other categories reflect the personal-agent side of Muse. Errands & personal agent gathers stories such as a $1,750 unclaimed property find, a $603-a-year car insurance saving, an Alaska flight claim filed from email receipts, and a portfolio-aware Muse feed. Business & commerce covers items like a Squarespace-to-Shopify migration and Shopify Catalog checkout inside Muse. Local & open models collects work on Muse Glimmer, including a free fine-tuning notebook that reports training it faster with less VRAM, and Apps & websites includes builds such as a Tinder-style interface for unfollowing people on Instagram. There is also an Agents & automation category, where projects like TerMuse — a tool that shows a Muse agent's live terminal and an interactive browser side by side — are listed.
The site's approach is deliberately indirect: it does not host the builds, run them, or re-publish their instructions. Instead it curates and links. Each listing is a pointer — the description summarises what the build does in a sentence or two, credits the creator by name and handle, and provides an outbound link to the original X post, Reddit thread, GitHub repository, YouTube video, blog resource or website. Visitors can therefore start from the catalog and end up at the primary source, whether that is a repository they can clone, a video they can watch, or a post they can read in full. Submissions are accepted through a dedicated submission page, and the homepage explicitly features newly submitted builds so recently published work gets visibility alongside the wider archive.
For anyone assessing Muse, the benefit is a shortcut to evidence. Instead of reading feature lists, visitors can see what has been built, what it cost, what the results looked like, and who did it — for example, a benchmark that measured Muse Spark 1.3 against frontier models on planted bugs, or a report that Muse Glimmer delivered five runnable games at roughly one-fifth of Muse Spark's cost. For builders, the directory is a source of inspiration and prior art: seeing that someone connected Linear in under a minute, taught Muse a custom connector, or drove the Unity CLI to port a game to VR makes it clearer what a next project could look like. And because every card links out, the catalog also acts as a discovery layer for the creators themselves, sending traffic and credit back to their posts, repositories and channels.
Concrete uses of ShipWithMuse follow from that structure. A developer new to Muse Code can browse the Coding & dev tools and Connectors & MCP categories to find setup guides, CLI walkthroughs and working connector examples before writing their own. Someone evaluating model performance can go straight to Benchmarks & research and read the collected tests and analyses in one place. A builder looking for project ideas can scan Games & 3D or Apps & websites for examples of what Muse produces in a single file or a short session. Teams curious about the personal-agent capabilities can read the Errands & personal agent entries — flight claims, insurance comparisons, unclaimed property searches — to understand what such workflows look like in practice. And creators can submit their own builds for listing in the catalog.
ShipWithMuse is maintained by @mohithkumar808, credited on the site as the curator. It is a web-based catalog. The site also sells sponsorship placements: a sponsored slot the same size as a post, shown every 12 builds on every catalog page, priced at $100 per week, and the site's sponsor strip includes ChatForm and Tgmlabs. The directory draws on a range of build types — X posts, Reddit posts, GitHub repositories, videos, sites, skills, resources and guides — and its Product Hunt listing classifies it under Productivity, Developer Tools and Artificial Intelligence.
The through-line is simple: ShipWithMuse turns scattered Muse activity into a single, link-backed catalog. By indexing more than a thousand real builds, letting visitors filter by type and highlight star picks, and pointing every entry at its original public source, it gives developers and observers a practical way to discover what Muse can do — and, if they have built something themselves, a place to submit it.