
Super Artifacts
io.github.Super-ArtifactsPublished by GitHub account Super-Artifactsv0.192.0Updated Nov 6, 2026
Publish live pages from any agent, collect what visitors submit, and read it back.
The publisher's own server: artifacts.boo
Overview
Hosted MCP server that lets an agent publish live web pages, forms and trackers, then read back what visitors submit.
- What you can do
- Publish artifacts at a stable URL, with new versions per slug, and stage large media files by URL
- List artifacts, versions and files, and change version, visibility, collection or deletion
- Read, aggregate and write visitor submissions, and inspect the data schema
- Manage collection entries, projects, sharing, comments and signature requests
- Find, save, install, rate and release templates
- Call an owner-approved API with a secret the agent never sees, and check which account the connection publishes as
- When to use it
- Useful when an agent builds something people should actually open — a form, tracker or walkthrough — and you want a live link plus a hosted place to collect and read responses without running your own backend.
- Requirements
- Remote MCP endpoint at superartifacts.app/mcp; no local package or runtime. Requires a Super Artifacts account and OAuth sign-in through your browser, where you approve the account the agent publishes to.
Installation
In SourceWeft
- Open Super Artifacts in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Super-Artifacts%2Fsuper-artifacts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"super-artifacts": {
"type": "http",
"url": "https://superartifacts.app/mcp"
}
}
}README
Turn what your agent builds into something people can use.
superartifacts.app · Docs · Pricing · Connect your agent
Super Artifacts is where the things your coding agent builds go to be opened. An agent publishes a page, a form, a tracker or a walkthrough, and gets back a live URL that works on a phone. Visitors can answer what you built, and your agent reads the answers back and can change the page, all through the same connection.
This repository is the public side of it: the MCP endpoint to point your agent at, the guides for each agent, and the plugin for each place agents are installed from: Claude, ChatGPT and Codex, and Hermes.
What it does
- It is data-driven. An artifact can declare what it collects. Visitors' answers land in a hosted database, and the agent that published it reads them back, as rows or as totals.
- It works across agents. Any agent that can talk to an MCP server connects to one URL and signs in through your browser. There is a guide for each one, linked below.
- Templates save tokens. When someone has already built the thing you want, your agent installs that template and fills it in instead of writing it again from nothing.
- Projects group artifacts. Put artifacts in an order, or let a rule fill the list, and present them one at a time from a single link.
Connect in 30 seconds
The MCP endpoint is the same for every agent, and it signs in over OAuth:
In Claude Code it is one command:
Your browser then opens a consent page that names the account the agent would publish to. Allow it only if it is yours. Connecting publishes nothing, and the key can be revoked from your agents page.
For any other agent, follow its own page. Each one lists the exact line that agent takes:
Claude Code · Claude Desktop · ChatGPT · Codex · Cursor · Windsurf · Zed · Gemini CLI · GitHub Copilot · Devin · Hermes · OpenClaw · Amp · Antigravity · Cline · Goose · Grok Build · Junie · Kilo Code · Kiro · Manus · OpenCode · Qwen Code · Warp
What it looks like
The screens below are the real product with demo data, in the order you meet them.
[The Authorize this connection page: Claude Code wants to publish artifacts to the account northlight, with Deny and Allow buttons.]
1. Connecting names the account first and lists what the key can and cannot do. Nothing is published yet.
[The Agents page of the Super Artifacts dashboard: Claude Code listed as a connected agent with its key, six artifacts and a Revoke key button.]
2. Once you allow it, the agent shows up on your Agents page, with a Revoke key button. (Demo data.)
[A published artifact open on a phone: a supper-club page with a three-course menu and a reservation form with name, evening and seat pickers.]
3. Ask for a page and you get a link that opens on a phone. (Demo data.)
[The Data page of an artifact in the Super Artifacts dashboard: a table of nine reservation responses.]
4. What visitors submit lands in a hosted database, the same rows your agent reads back with super_data. (Demo data.)
[The Gallery in the Super Artifacts dashboard: six artifacts in a list, each with its title, visibility and version.]
5. Everything it publishes, in one gallery, private unless you open it. (Demo data.)
[The Versions tab of an artifact: v3 live, with v2 and v1 below it and a Restore this version button on each.]
6. Publish again at the same slug and it becomes a new version; any earlier one can be restored. (Demo data.)
The twenty tools
Your agent gets these over MCP. One noun each, and super_help returns short usage notes on demand.
Plugins
Each plugin is the same hosted MCP server and nothing else: no slash commands, no scripts, no code runs on your machine. Install one, sign in once over OAuth, and ask your agent in your own words.
Send the two Claude Code prompts separately. Updates install themselves: a git-hosted marketplace updates in the background.
Not sure what to ask first? Try one of these:
- "Publish a one-page supper-club reservation form and give me the link."
- "Show me what people have submitted to my reservation page."
- "Add a vegetarian option to my reservation form and publish a new version."
Connecting publishes nothing. Your agent builds only what you ask for, and artifacts stay private until you open them on the artifact's own page.
Status
The hosted product is live at superartifacts.app. This repository is a read-only mirror of the three plugins and the connect guides, regenerated from the private source repository on every change to them, so commits made here are overwritten. The plugins are at the version in plugin.json.
Licence
MIT. See LICENSE.
Source: README.md at commit a81b5f3
Tools
0Version history
4- v0.192.0LatestNov 6, 2026
- v0.190.0Nov 6, 2026
- v0.189.1Nov 5, 2026
- v0.189.0Nov 5, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Artifacts integrations

artifacts.boo
boo.artifactsOfficial publisher
Lets an assistant publish small interactive pages in a team workspace, where invited people comment, approve and fill in answers the agent can read back.

attest — verification for AI agent artifacts
Published by GitHub account mrpkk
Remote MCP server that verifies artifacts produced by AI agents — schema, emptiness, provenance and authority — and returns a signed verdict.

Artifacts
Published by GitHub account mctx-ai
Artifacts is a remote MCP server that lets an assistant save decisions, plans and notes from an AI session and retrieve them later from any client.

Artifacts
Published by GitHub account kuyazee
Lets an assistant publish HTML, JSX, Markdown, PDF, or zipped static sites to a self-hosted server and return an unguessable URL on your own domain.

Reviewable Artifacts
Published by GitHub account garrietv
A local stdio MCP server that lets an assistant discover reviewable workspaces and create private HTML reviews.