Super Artifacts

io.github.SuperbeltPublished by GitHub account Superbeltv0.244.0Updated Nov 16, 2026

Publish live pages from any agent, collect what visitors submit, and read it back.

The publisher's own server: artifacts.boo

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & StorageData & Analytics

Overview

AI-generated overview

Lets an agent publish live web pages, forms and trackers at stable URLs, then read back what visitors submit and revise the page.

What you can do
  • Publish artifacts such as pages, forms, trackers and walkthroughs at a stable URL, with new versions per slug and rollback
  • Stage images, video and other large files by URL so a publish carries them
  • List artifacts, versions and files, and change version, live state, visibility, collection or deletion
  • Read, query and write visitor submissions, inspect the data schema, and manage collection entries
  • Find, save, install, rate and release templates, and group artifacts into projects
  • Share artifacts, read and answer comments, request signatures, manage webhooks, and check which account the connection publishes as
When to use it
Useful when a coding agent builds something people should actually open and use, such as a reservation form, tracker or walkthrough, and you want the submissions back in the same session. Also fits teams that want to reuse templates and group artifacts into ordered projects.
Requirements
A remote MCP endpoint at superartifacts.app/mcp reached over streamable HTTP, with OAuth sign-in through a browser consent page naming the publishing account. No packages, environment variables or headers are declared.
Before you install
The OAuth grant lets the connected agent publish and change artifacts under your account, so approve only your own account and revoke the key from the agents page when done. Tools can write and delete data, change visibility, share artifacts and manage webhooks; artifacts are private until opened. super_secret_use calls an owner-approved API with a secret the agent does not see.

Installation

In SourceWeft

  1. Open Super Artifacts in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.Superbelt%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.

Read the install guide the agent follows

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

[Super Artifacts]

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:

text
https://superartifacts.app/mcp

In Claude Code it is one command:

bash
claude mcp add --transport http super-artifacts https://superartifacts.app/mcp

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-one tools

Your agent gets these over MCP. One noun each, and super_help returns short usage notes on demand.

ToolWhat it is for
super_publishPublish an artifact at a stable URL. The same slug makes a new version.
super_uploadStage images, video and other big files by URL, so a publish carries them without their bytes passing through the agent.
super_artifactsList your artifacts, their versions and their files, or open a private one in a browser for ten minutes.
super_artifact_setChange what an artifact serves and to whom: version, live, visibility, collection, delete.
super_dataRead what visitors submitted.
super_data_queryAggregate what was collected.
super_data_writeWrite rows into your artifact's data as the owner: create, replace or delete the rows you wrote.
super_data_schemaSee what data exists and what it means.
super_entriesRead or write a collection's entries.
super_secret_useCall one API the owner approved with a secret the agent never sees.
super_templatesFind, list and read templates.
super_template_saveCreate or revise a template draft.
super_template_actionInstall, uninstall, rate, report or roll back a template.
super_release_templateMake one version of your template available to everyone who installed it.
super_projectCreate, read and edit projects.
super_shareGive people access.
super_commentsRead and answer the comments on an artifact.
super_signaturesAsk people to sign a published version, and track who has. It cannot sign for anyone.
super_whoamiShow which account and agent this connection publishes as.
super_webhooksManage webhook endpoints for your agent and read recent messages.
super_helpHow the tools fit together.

Plugins

All three plugins connect to the same hosted MCP server. Claude and OpenAI carry no executable code. Hermes also carries a dashboard connection page and Python backend, plus a workflow skill and secret settings schema. Install, connect, and ask your agent in your own words.

ForFolderInstall
Claude Code, Claude Desktop, Cowork and claude.aisuper-artifacts//plugin marketplace add Superbelt/plugins, then /plugin install super-artifacts@super-artifacts
ChatGPT and Codexopenai/codex plugin marketplace add Superbelt/plugins; ChatGPT installs from its plugin directory
Hermes Agenthermes/hermes plugins install super-artifacts --enable, then Connect in the Super Artifacts dashboard tab

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 d8cf5d4

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

7
  1. v0.244.0LatestNov 16, 2026
  2. v0.241.0Nov 16, 2026
  3. v0.240.0Nov 16, 2026
  4. v0.238.0Nov 15, 2026
  5. v0.236.3Nov 15, 2026
  6. v0.236.1Nov 15, 2026
  7. v0.236.0Nov 15, 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