An agent builds it. Somebody opens it.
Your agent builds something in a folder and deploys it to a live URL in seconds. Real people open it on their phones, use it, and what they do flows back to the agent that built it.
claude mcp add --transport http super-artifacts \
https://api.superart.page/mcpOne MCP URL, one consent click, and your agent publishes at a URL a reviewer opens on a phone.
What makes an artifact super
The artifact a visitor opens is the evidence. Each of these is a crop of the real product, at the width it is actually used.
Data driven
- A form the artifact renders writes into a database that comes with the artifact — one field on the deploy, nothing to set up.
- The agent that built the artifact reads the rows back over MCP, the same session that shipped it.
- Every row is attributed to the visitor who submitted it, and erasing a visitor erases their rows on both planes.
Seamless collaboration
- Comment on any artifact; the comments live beside it, not in a thread somewhere else.
- Invite somebody, and their agent can read the artifact, its data, and the comments.
- An agent that reads the comments can build the next version — the feedback loop runs through the artifact itself.
Interoperable
One agent creates; another reads the artifact, its data, or a collaborator’s comments. Agentic tools talk to each other through artifacts — the MCP surface is the same one your harness already speaks, so nothing new is installed.
How it works
Three moves, and only the first one involves you.
Connect an agent
Point the harness at one MCP URL. It speaks OAuth itself — the harness offers a Connect button, the consent screen names the account, and the key stays in the harness where you can revoke it.From the harness the agent already runs in claude mcp add --transport http super-artifacts https://api.superart.page/mcpIt deploys what it built
A folder of files becomes an address. The bytes the agent sends are the bytes that get served — there is no bundler, no framework convention, and nothing to configure.One request, no build step curl -sS -X POST https://api.superart.page/deploy \ -H "Authorization: Bearer $SUPER_ARTIFACTS_KEY" \ -d @deploy.jsonYou decide who can open it
A fresh deploy is readable by you and nobody else. Name the people who should see it, or make it public on purpose. Either way it is a decision you took, not a URL that got forwarded.
Start from a template, not from scratch
A template is the pattern an artifact is built from, not the artifact itself: install one and your agent starts from a shape that already works — the fields, the data policy, the craft guidance — instead of inventing all three. That is fewer tokens spent finding the form and better results inside it.
Slideshows organize artifacts to tell a story: a deck a visitor advances through, assembled from work that already exists.
The table stakes, done
The platform does the rest: hosting, version history that moves a pointer rather than redeploying, and a URL you can share.
- DeployOne request turns a folder of files into a URL somebody can open on a phone.
- VersionsPublishing moves a pointer. Rolling back and rolling forward are one operation.
- AccessPrivate by default. Sharing is a grant you make, never a URL that leaked.
- AnalyticsWhether anyone read it, on what, and whether it threw an error while they did.
- AgentsOne line pairs an agent. It fetches its own instructions and deploys on its own.
Pricing
Free to start. Pro is $19 a month, with a 14-day trial.
Enough to build a few things and share them with people you name.
For someone shipping artifacts continuously rather than occasionally.
Shared ownership across a group, on one bill.
Questions
The honest answers, including the ones about what is not finished.