A bundle is just a URL now

For a while, "here's my MCP setup" meant a screenshot, or a paragraph in a chat thread explaining which servers to wire together and in what order. That doesn't compose. You can't fork a screenshot.

Bundles can now live at a real, public URL - /bundle/[id] - readable by anyone, no account required. That sounds small; we think the more interesting shift is underneath it: a bundle stops being "your private config" and starts being a shareable artifact, the same way a gist or a docker-compose.yml is. Someone posts a link, you open it, you see exactly what's in it, and if you like it you fork it into your own account with one click instead of retyping a list of server names from memory.

A few things we were deliberate about:

• Read is free, write isn't. Anonymous visitors get the full read-only view - description, tags, every MCP in the bundle - but the moment an action would change anything, even just following it, we ask you to sign in. No silent partial state.
• 404 means 404. A private or nonexistent bundle id returns a real HTTP status, not a "this bundle doesn't exist" message wrapped in a 200. That distinction matters more than it sounds like once crawlers, link previews, and monitoring are all in the mix.
• Forking is tracked, not just copied. Every fork keeps a pointer back to what it came from, and the original shows a fork count. If bundles become the unit people actually share, provenance is worth keeping from day one rather than bolting on later.

Bet: as more of what people build is "an agent plus a specific set of tools," the shareable unit won't be a repo or a README - it'll be a link like this one.

Full mechanics are in the public bundle docs.