Any artifact made from trackers
Trackers
A form a visitor fills over time, and the history builds behind it — declared as measurements, so the units are checked at the edge.
Never start from a blank page
Every card below is a working template, already wired up. Copy its prompt, hand it to your agent, and it customizes the pattern from there instead of building one from nothing.
What makes Super Artifacts super
Real data, retained the right way
Every artifact is backed by structured data, not a static page, captured through a compliance-aware pipeline so what visitors submit is retained the way it has to be.
Works with whichever agent you're using
An artifact is not tied to the agent that built it — any MCP-speaking agent can read it and pick up the work, so switching tools never costs you what you already made.
Templates save tokens
Starting from a template instead of a blank page means less back-and-forth generation, so every artifact you build from one costs fewer tokens.
Playlists keep artifacts organized
Group related artifacts into a playlist so a set stays easy to find and reuse, instead of scattering as one-off links nobody can relocate.
Your first artifact is one conversation away
Connect the agent you already use, describe what you want, and it is live at a URL a reviewer opens on a phone.
No MCP support in your agent? Install the skill instead
Frequently asked questions
Something your agent builds and deploys to a URL people open — a tracker, a survey, a playlist. Not a transcript you have to explain, and not a code block somebody has to run: a page.
Those render something in a window you look at. A super artifact is deployed at a URL with a database behind it, so real people can open it on their phones, use it, and have what they typed flow back to the agent that built it. It is the same idea, plus the half those tools stop at: the data loop.
One MCP URL. Point the harness at it —
claude mcp add --transport http super-artifacts https://api.superart.page/mcp— the harness offers a Connect button, the consent screen names the account, and the key stays in the harness where you can revoke it.Into a database that comes with the artifact. What the artifact may collect and who may read it is a policy the deploy declares, enforced per row: an artifact that says a visitor reads only their own entries cannot hand them anybody else’s, and an artifact marked private serves nothing to somebody who has not been named.
Erasing a visitor erases their rows on both the serving plane and in the database, and deleting an artifact closes the whole surface behind it.
No. Every byte comes out of your agent’s model, on your tokens, in your environment. There is no endpoint here that takes a prompt and returns a page, and there is not going to be one — an agent that expects the platform to generate the artifact will post a prompt and get back an empty page.
There is no per-artifact analytics report yet — the view and error pipelines are live and the gallery shows counts, but the page that breaks them down is not built. There is no
supercommand-line tool, only the HTTP endpoint it would wrap. Custom domains are not built either, which is why they are not listed as a Solo feature.