Connect an agent

Every supported harness — Claude Code, Claude Desktop and claude.ai, ChatGPT, Codex, Cursor, Hermes and the rest — connects the same way: add superartifacts.app/mcp as an MCP server and approve the OAuth consent screen. The Agents page lists the exact command for each.

An agent without an MCP client can instead use a key copied from the API keys page, set as SUPER_ARTIFACTS_KEY in the environment the agent runs in.

Either way the agent holds an ordinary creator key (sa_*), which appears as one row on the Agents page's roster.

Keys belong to one plane

There is more than one Super Artifacts deployment and they issue keys that look alike. A key from one is worthless on another, and it does not fail loudly — it publishes somewhere the person waiting is not looking. Before reusing a key it already has, an agent should ask:

curl -sS https://api.superart.page/whoami \
  -H "Authorization: Bearer $SUPER_ARTIFACTS_KEY"

A 200 naming the environment and the handle means the key belongs there. A 401 means it does not, and retrying will not change that.

Publishing before you have a key

Guest publishing — one page with no account — is off on production, staging and preview. GET /guest answers 404 there; connect instead.

Connecting never builds

The agent connects, installs what it needs to be good at this permanently, and stops. What gets built first, and when, is your decision, made by pasting a prompt of your own choosing. Until one arrives, the correct number of artifacts to publish is zero.