MCP tools

One address, superartifacts.app/mcp, and eighteen tools your agent calls for you: what each one does, and a prompt that reaches it.

reference~3 minVerified v0.66.1

Your agent reaches Super Artifacts through one address, its MCP server. Connect once and the agent can publish, read and share for you.

Connect

Pick your agent and copy the prompt. Paste it into the agent; it does the setup and asks you only for what needs your hands, such as clicking Allow in the browser.

Copy the install prompt, then paste it at Claude Code. It does the connecting itself.

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://pr-764-stg.superartifacts.app/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://pr-764-stg.superartifacts.app/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://pr-764-stg.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.

If your app adds connectors in its settings instead, give it this address:

code

https://superartifacts.app/mcp

The Agents page has the steps for each agent and lists every agent you have connected.

Eighteen tools

Tool	Does	Example prompt
`super_whoami`	Who am I publishing as	Which Super Artifacts account are you publishing to?
`super_publish`	Publish an artifact	Publish this page and send me the link.
`super_upload`	Stage files for a publish	Publish these screenshots in a page. Upload the files, do not paste them.
`super_artifacts`	Your artifacts, their versions and files	List my artifacts and open the newest one so I can see it.
`super_artifact_set`	Change what an artifact serves, and to whom	Put version 3 of the launch page back live.
`super_data`	Read what visitors submitted	Show me every RSVP people sent.
`super_data_query`	Aggregate what was collected	How many RSVPs said yes, by dietary need?
`super_data_write`	Write rows into your artifact	Fill the recital program with these ten pieces.
`super_data_schema`	What data exists, and what it means	What data do my artifacts collect, and what does each field mean?
`super_entries`	Read or write a collection's entries	Add these five products to my Catalogue collection.
`super_templates`	Find, list and read templates	Find me a template for a weekly team update.
`super_template_save`	Create or revise a template draft	Turn this artifact into a template draft.
`super_template_action`	Install, uninstall, rate, report or roll back a template	Install the retro board template.
`super_release_template`	Make one version of your template everybody’s	Release my retro board template to the marketplace.
`super_project`	Create, read and edit projects	Put my three launch pages in a project called Launch, in this order.
`super_share`	Give people access	Share the Q3 report with dana@example.com.
`super_comments`	Read and answer the comments on an artifact	Read the open comments on the launch page and answer them.
`super_help`	How the tools fit together	How do projects and collections differ?

You never call these yourself: you ask, and your agent picks the tool. Old tool names from before 29 September 2026 are deprecated but still resolve; use the current names.

Every answer has the same shape

What a tool sends back to your agent:

json

{ "ok": true, "next": [{ "tool": "super_artifacts", "args": {}, "why": "…" }] }
{ "ok": false, "code": "invalid_arguments", "message": "…", "fix": "…", "accepts": ["…"] }

ok says whether it worked. When it did not, code names the problem (Error codes), message explains it, fix says what to change and accepts lists the arguments the tool takes. When it did, next suggests the likely next step. Your agent reads all of this, so a refusal is something it can act on.

Timeouts

A call that has not answered after 55 seconds comes back as mcp_timeout. It may still finish. Reading is safe to repeat; a change, such as a publish, may already have happened, so have your agent check before it tries again, or the page is published twice:

After a timeout

That Super Artifacts call timed out. Before you try again, check with super_artifacts whether it already happened, and only redo it if it did not.

Until 11 October 2026 this gave up at 25 seconds with a bare error instead.