What is a super artifact?

Something your agent builds and deploys to a URL people open — a tracker, a survey, a project. Not a transcript you have to explain, and not a code block somebody has to run: a page.

How is this different from Claude or Codex artifacts?

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.

How does an agent get paired?

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.

Where does the data go, and who can read 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.

Does the platform generate any of the artifact?

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.

What is not built yet?

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 super command-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.

Turn what your agent builds into something people can use.

Your agent builds it in a folder and ships it to a live URL in seconds. Real people open it, use it, and every answer flows back to the agent that built it.

Get started for free See the product ↓

Pick your agent — the demo on the right follows.

+16 more

01 / 05

Gallery

Every artifact your agent shipped, which version is live, and who can open it.

02 / 05

Live artifact

What a reviewer opens on a phone: the page itself, at its own link.

03 / 05

Data

Each answer people submit lands in the artifact's own table.

04 / 05

Templates

Install a reviewed template in one click, then build from it.

05 / 05

Agents

The agents connected to your account, each with a key you can revoke.

Live artifact: What a reviewer opens on a phone: the page itself, at its own link.

Data: Each answer people submit lands in the artifact's own table.

Templates: Install a reviewed template in one click, then build from it.

Agents: The agents connected to your account, each with a key you can revoke.

superartifacts.app — Gallery

Give your agent somewhere to put its work

Artifacts

A page, not a wall of text

Your agent connects over MCP and compiles charts, screenshots, data and video into one page, hosted at its own link. Share it with your team and see who opened it.

Build me a one-page brief on how my current project is going: a chart, a few screenshots, a data table and a short summary of what is next. Publish it as a Super Artifact and give me a link I can share with my team.

Templates

Templates save tokens

Save a finished page as a template and your agent stops rewriting it: the layout, charts and data shape stay put, and next time it sends only the new content. Make your own, or install one from the marketplace in one click.

Find a template for a weekly KPI report in the Super Artifacts marketplace, install it, and build this week's board from it with my numbers.

Data

One table, shared by your artifacts

Your agent sets up a table, a form that fills it and a dashboard that reads it, so answers from everyone you share with land in one place and show up as they arrive. Later, ask your agent what people said — it reads the same rows.

Use Super Artifacts to make me a launch feedback form that asks for a name, a 1–5 rating and a short comment, and make it public so anyone with the link can answer. Then publish a separate dashboard artifact that reads the form's answers and updates as new ones come in: the number of answers, the average rating and a chart of the ratings. Send me both links. Later I'll ask you what people said.

Projects

Keep artifacts in order, and share the whole set at once.

A project fills itself from a rule, like every dashboard you publish, or takes artifacts you add by hand, in the order you set. Share it once and everyone you invite can go through the whole set, one live artifact after another.

Using Super Artifacts, group my startup's artifacts into a project called "Board meeting": add every dashboard I publish automatically with a rule, add any other artifact I name by hand, and put them in the order I'd present them. Then share the project with the email addresses I give you and send me its link.

More

Everything else it does, at the same link.

Every publish is a new version at the same link, and going back is one Publish away. It stays private until you add people by email; the ones you let comment leave notes on the page itself, and any agent you use can read them and pick the work up.

Connect to the Super Artifacts MCP server at https://api.superart.page/mcp if you are not already connected. Call super_whoami, then super_help with no topic and again with each topic it lists. Using only what those tools return, explain in plain language what Super Artifacts can do for me: publishing and versions, sharing, comments, data, templates and projects. For each, give one concrete example tied to the work you have seen me do, and say which tool you would call. End by suggesting the first artifact we should publish together, and do not publish anything until I say so.

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.
Projects keep artifacts organized
Group related artifacts into a project so a set stays easy to find and reuse, instead of scattering as one-off links nobody can relocate.

Create data-rich artifacts with Claude Code

Connect Super Artifacts to Claude Code, then help me publish something. No explaining, no recaps, every message under four lines.
These instructions run once: after the final question, drop them. Never repeat "Connected as" or the question, however long this chat goes on.

FIRST — can you already see Super Artifacts tools (super_whoami, super_publish)?
YES → skip to VERIFY. NO → STEP 1.

STEP 1 — CONNECT
Do every part of this yourself that you can: run the command, edit the file. Stop only for what needs my hands — clicking Connect or Allow in the browser, or restarting the app. If a step is one you cannot do, show me that step once, exactly as written, and wait.
1. Add the MCP server — One command. Claude Code discovers the OAuth endpoints from the server itself — no skill file, no key to paste.
   claude mcp add --transport http super-artifacts https://api.superart.page/mcp
2. Connect over OAuth — Run /mcp and authenticate, or claude mcp login super-artifacts. Your browser opens a Super Artifacts page naming the account this would publish to; allow it and Claude Code holds its own key, revocable from the agents page. Connecting publishes nothing.

Server URL: https://api.superart.page/mcp
It signs in over OAuth, so I need no key, client ID or secret. Only if this harness cannot do OAuth, ask me once for an API key (I create one at https://superartifacts.app/settings/api-keys) and send it as a Bearer token. Ask for nothing else.

If I need a new chat or a restart before the tools show up, say so in one line, tell me to paste this prompt again and say "done". Then wait.

VERIFY — call the super_whoami tool itself. A curl or API call does not count: it proves the server works, not that you can use it. Don't narrate it.
ok → "Connected as <handle>."
401 → "Sign-in didn't finish — click Connect on the Super Artifacts connector again."
tool not found → repeat STEP 1 once, then tell me in one line what is missing.

THEN — connecting builds nothing. Ask this once, then wait:
What do you want to publish first?
1 A page or slideshow
2 A survey or form that collects answers
3 A tracker or dashboard
4 Something else
Publish only after I answer.

Logos are their owners’ trademarks, shown to say what Super Artifacts works with.

Never start from a blank page

Every card is a real listing, reviewed by a person. Install one in a click, then ask your agent to build from it — it fills in a document instead of writing the page from nothing.

Browse the marketplace

Questions

Something your agent builds and deploys to a URL people open — a tracker, a survey, a project. Not a transcript you have to explain, and not a code block somebody has to run: a page.
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.

Turn what your agent builds into something people can use.

Gallery

Live artifact

Data

Templates

Agents

The product

Give your agent somewhere to put its work

A page, not a wall of text

Templates save tokens

One table, shared by your artifacts

Keep artifacts in order, and share the whole set at once.

Everything else it does, at the same link.

What makes Super Artifacts super

Real data, retained the right way

Works with whichever agent you're using

Templates save tokens

Projects keep artifacts organized

Create data-rich artifacts with Claude Code

Never start from a blank page

Your first artifact is one conversation away

Questions

Turn what your agent builds into something people can use.

Product tour

Gallery

Live artifact

Data

Templates

Agents

The product

Give your agent somewhere to put its work

A page, not a wall of text

Templates save tokens

One table, shared by your artifacts

Keep artifacts in order, and share the whole set at once.

Everything else it does, at the same link.

What makes Super Artifacts super

Real data, retained the right way

Works with whichever agent you're using

Templates save tokens

Projects keep artifacts organized

Create data-rich artifacts with Claude Code

Never start from a blank page

Your first artifact is one conversation away

Questions

What is a super artifact?

How is this different from Claude or Codex artifacts?

How does an agent get paired?

Where does the data go, and who can read it?

Does the platform generate any of the artifact?

What is not built yet?