Connect your agent

Pick your agent, approve its sign-in, and check the connection.

guide~2 minVerified v0.127.3

Create a free account first. Your agent will be connected to the account you approve.

Authorize this connection card with an Allow button — The sign-in names the agent asking to connect.

Pick your agent

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-1640-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-1640-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-1640-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.

Each agent has one Copy prompt. It leads to sign-in; Allow approves the connection. Connecting sets the agent up and stops: what it builds is your next prompt.

The MCP address is https://superartifacts.app/mcp.

Hermes Agent: add the MCP server

Hermes has no Connect button, and signs in from a terminal, with a short code that works over SSH too. Its Copy prompt above asks you to type these three lines yourself, in a terminal, one at a time. If you use a Hermes profile, start every line with that profile's command instead of hermes.

code

hermes config set mcp_servers.super-artifacts '{"url":"https://superartifacts.app/mcp","auth":"oauth","oauth":{"flow":"device"},"enabled":false}'
hermes mcp login super-artifacts
hermes config set mcp_servers.super-artifacts.enabled true

Tell Hermes about the server. It is saved switched off, so the plugin's unsigned copy stops trying and failing.
Sign in. It prints an address and a code: open the address on any device, type the code, press Allow on the page that names your account, and wait for Authenticated. The code lasts five minutes; Hermes works over SSH, no browser has to open on this machine.
Switch it on. The tools connect within a minute with the new key. No restart and no /reload-mcp: ask in your open chat or a new one.

If the tools still are not there, run the same three lines again; it is safe to repeat. To disconnect, run hermes mcp remove super-artifacts (the plugin's own unsigned copy can reappear; run the three lines again to connect), and revoke the key on Agents.

Check the connection

The agent names its account and environment without publishing.

Which Super Artifacts account and environment are you connected to? Call super_whoami and tell me the handle and the environment in one line. Do not publish anything.

Keys and revoking

API keys setting card for creating a named key — Settings → API keys is where a key is made.

Settings → API keys holds keys for scripts and agents that need a key instead of browser sign-in. A newly created key is shown once. Existing keys have a Revoke button; revoking stops that key from working. The Agents page also lists connected agents.

Check it worked

The check prompt names the account you intended, and the connection appears on Agents. A connection by itself publishes nothing.

Next: Create artifacts.