# Connect your agent > Pick your agent, approve its sign-in, and check the connection. Kind: guide · ~2 min · Verified v0.71.0 · Next: [Create artifacts](https://pr-767-stg.superartifacts.app/docs/create.md) Your agent will be connected to the account you approve. ![Authorize this connection card with an Allow button](https://pr-767-stg.superartifacts.app/screenshots/docs/connect-consent-light.0dd38344.webp) *The sign-in names the agent asking to connect.* ## Pick your agent ### Claude Code ```prompt 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-767-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-767-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-767-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 ." 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. ``` ### Claude Desktop & claude.ai ```prompt Connect Super Artifacts to Claude Desktop & claude.ai, 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 connector — Settings → Connectors → Add custom connector, and paste this URL. Anthropic’s cloud calls it, not your machine, so it has to be a public address — which this is. https://pr-767-stg.superartifacts.app/mcp 2. Then connect it over OAuth — Claude will offer a Connect or Sign in button for the connector. That opens a Super Artifacts page asking whether to let it publish here, and names the account it would publish to. Allow it and the connector holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### ChatGPT ```prompt Connect Super Artifacts to ChatGPT, 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. Turn on developer mode — Settings → Apps → Advanced settings, on the web app. Available on ChatGPT Plus, Pro, Business, Enterprise and Edu plans. 2. Add the connector — Add a custom connector pointing at this URL. It speaks Streamable HTTP, which is what ChatGPT expects from a remote MCP server. https://pr-767-stg.superartifacts.app/mcp 3. Then connect it over OAuth — ChatGPT offers a sign-in for the connector. It opens a Super Artifacts page naming the account this would publish to; allow it and the connector holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Codex ```prompt Connect Super Artifacts to Codex, 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 line in config. Codex discovers the OAuth endpoints from the server itself; the config it writes is shared by the CLI, the IDE extension and the desktop app. codex mcp add super-artifacts --url https://pr-767-stg.superartifacts.app/mcp 2. Connect over OAuth — Run codex mcp login super-artifacts (or /mcp in the TUI). Your browser opens a Super Artifacts page naming the account this would publish to; allow it and Codex holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Hermes ```prompt Connect Super Artifacts to Hermes, 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 You are in a chat with no browser, so Hermes signs in with a code: you run the command, show me the address and the code it prints, and I approve it on any device. Never register a client, build an authorize URL or write a token file by hand. 1. Add the MCP server — Add this under mcp_servers in the profile's config. Hermes discovers the OAuth endpoints from the server itself. mcp_servers: super-artifacts: url: https://pr-767-stg.superartifacts.app/mcp auth: oauth oauth: flow: device 2. Sign in with a code — Hermes cannot open a browser from a chat, so it signs in with a code: run this, keep it running, and show the person the web address and the short code it prints. They open the address on any device, type the code and press Allow on the Super Artifacts page naming the account this would publish to — that is the whole step. The command waits up to five minutes; if it times out, run it again for a fresh code. Hermes holds its own key afterwards, revocable from the agents page. Connecting publishes nothing. hermes mcp login super-artifacts --flow device 3. Load the tools — The person sends /reload-mcp in the chat — a slash command only they can send. No restart is needed: the session and its history stay. Server URL: https://pr-767-stg.superartifacts.app/mcp If sign-in fails twice, stop. Tell me to create a key at https://pr-767-stg.superartifacts.app/settings/api-keys and save it as SUPER_ARTIFACTS_KEY in ~/.hermes/.env myself, then change the server entry to read it: headers: Authorization: Bearer ${SUPER_ARTIFACTS_KEY} Never ask me to paste a key into the chat. 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 ." tool not listed → "Tools not loaded — send /reload-mcp." Do not say connected. 401 → "Sign-in didn't finish — run the sign-in step again." 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. ``` ### OpenClaw ```prompt Connect Super Artifacts to OpenClaw, 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. Save the MCP server — One command. OpenClaw saves the definition into its own config, ready for every runtime it projects into. openclaw mcp set super-artifacts '{"url":"https://pr-767-stg.superartifacts.app/mcp","transport":"streamable-http","auth":"oauth"}' 2. Connect over OAuth — Run openclaw mcp login super-artifacts. Your browser opens a Super Artifacts page naming the account this would publish to; allow it and OpenClaw holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Cursor ```prompt Connect Super Artifacts to Cursor, 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 — Paste this into ~/.cursor/mcp.json (or .cursor/mcp.json for one project). Cursor discovers the OAuth endpoints from the server itself. { "mcpServers": { "super-artifacts": { "url": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Cursor prompts to authenticate the first time the server is used — approve it and your browser opens a Super Artifacts page naming the account this would publish to. Allow it and Cursor holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### GitHub Copilot ```prompt Connect Super Artifacts to GitHub Copilot, 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. Copilot CLI stores it in ~/.copilot/mcp-config.json; the docs page also covers the /mcp add form in an interactive session. copilot mcp add --transport http super-artifacts https://pr-767-stg.superartifacts.app/mcp 2. Connect over OAuth — Copilot prompts to authenticate when the server is first used — approve it and your browser opens a Super Artifacts page naming the account this would publish to. Allow it and Copilot holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Gemini CLI ```prompt Connect Super Artifacts to Gemini CLI, 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 — Paste this into ~/.gemini/settings.json (or .gemini/settings.json for one project). The CLI discovers the OAuth endpoints from the server itself. { "mcpServers": { "super-artifacts": { "httpUrl": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Run /mcp auth super-artifacts. Your browser opens a Super Artifacts page naming the account this would publish to; allow it and the CLI holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Windsurf ```prompt Connect Super Artifacts to Windsurf, 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 — Add it in Settings → Cascade → MCP Servers (or paste this into ~/.codeium/windsurf/mcp_config.json). Windsurf discovers the OAuth endpoints from the server itself. { "mcpServers": { "super-artifacts": { "serverUrl": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Windsurf prompts to authenticate when the server is first used — approve it and your browser opens a Super Artifacts page naming the account this would publish to. Allow it and Windsurf holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Zed ```prompt Connect Super Artifacts to Zed, 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 context server — Settings → AI → MCP Servers → Add Server → Add Remote Server (or paste this into settings.json). Zed discovers the OAuth endpoints from the server itself. { "context_servers": { "super-artifacts": { "url": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Zed prompts to authenticate because the server entry carries no Authorization header — approve it and your browser opens a Super Artifacts page naming the account this would publish to. Allow it and Zed holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Devin ```prompt Connect Super Artifacts to Devin, 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. Devin infers the Streamable HTTP transport from the URL and saves it to user scope so every project sees it. devin mcp add super-artifacts https://pr-767-stg.superartifacts.app/mcp 2. Connect over OAuth — Run devin mcp login super-artifacts. Your browser opens a Super Artifacts page naming the account this would publish to; allow it and Devin holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Grok Build ```prompt Connect Super Artifacts to Grok Build, 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, or add a [mcp_servers.super-artifacts] block with a url field directly to ~/.grok/config.toml. grok mcp add --transport http super-artifacts https://pr-767-stg.superartifacts.app/mcp 2. Connect over OAuth — A server that needs OAuth triggers the browser flow the first time Grok Build calls it — no separate login command. Allow the Super Artifacts page naming the account this would publish to; the token is stored under ~/.grok/mcp_credentials.json and is revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Antigravity ```prompt Connect Super Artifacts to Antigravity, 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 — Paste this into ~/.gemini/config/mcp_config.json (or .agents/mcp_config.json for one project) — the IDE and CLI both read it. In the IDE you can instead use the "..." menu → Manage MCP Servers → View raw config. { "mcpServers": { "super-artifacts": { "serverUrl": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Open Agent Settings and click Authenticate beside the server. Your browser opens a Super Artifacts page naming the account this would publish to; allow it and Antigravity holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### OpenCode ```prompt Connect Super Artifacts to OpenCode, 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 — Add this under mcp in opencode.jsonc (project) or the global config. The empty oauth object turns on automatic OAuth handling. { "mcp": { "super-artifacts": { "type": "remote", "url": "https://pr-767-stg.superartifacts.app/mcp", "oauth": {} } } } 2. Connect over OAuth — Run opencode mcp auth super-artifacts. Your browser opens a Super Artifacts page naming the account this would publish to; allow it and OpenCode holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Goose ```prompt Connect Super Artifacts to Goose, 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 extension — Run goose configure → Add Extension → Remote Extension (Streamable HTTP), and give it this URI. The CLI and Goose Desktop share one config file, so it shows up in both. https://pr-767-stg.superartifacts.app/mcp 2. Connect over OAuth — No sign-in window appears until Goose actually opens the extension, so start a new session. Your browser opens a Super Artifacts page naming the account this would publish to; allow it and Goose holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Cline ```prompt Connect Super Artifacts to Cline, 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. Open an artifact-scoped key — Cline's docs describe remote servers authenticating with a bearer header, not an OAuth consent screen — generate a key from the agents page first. 2. Add the MCP server — MCP Servers → Configure → Configure MCP Servers opens cline_mcp_settings.json. Add this block with the key from the previous step. { "mcpServers": { "super-artifacts": { "type": "streamableHttp", "url": "https://pr-767-stg.superartifacts.app/mcp", "headers": { "Authorization": "Bearer " } } } } Server URL: https://pr-767-stg.superartifacts.app/mcp This harness takes a key, not OAuth: ask me once for an API key (I create one at https://pr-767-stg.superartifacts.app/settings/api-keys), put it where the steps say, and never print it back. 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 ." 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. ``` ### Amp ```prompt Connect Super Artifacts to Amp, 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. Amp manages the remote definition through ampcode.com rather than a local settings file. amp mcp remote add super-artifacts https://pr-767-stg.superartifacts.app/mcp --auth oauth --personal 2. Connect over OAuth — The command opens your browser to a Super Artifacts page naming the account this would publish to; allow it and Amp holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Kiro ```prompt Connect Super Artifacts to Kiro, 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 — Paste this into .kiro/settings/mcp.json for one workspace, or ~/.kiro/settings/mcp.json to make it global. Kiro discovers the OAuth endpoints from the server itself. { "mcpServers": { "super-artifacts": { "url": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Kiro prompts to authenticate the first time a tool is used — approve it and your browser opens a Super Artifacts page naming the account this would publish to. Allow it and Kiro holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Junie ```prompt Connect Super Artifacts to Junie, 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 — Settings → Tools → Junie → MCP Settings, then edit the mcp.json this opens (or add .junie/mcp/mcp.json to the project root by hand). Junie reads the same "mcpServers" shape most MCP clients use. { "mcpServers": { "super-artifacts": { "url": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Junie follows whatever auth the server asks for — this one challenges with OAuth on first use, so your browser opens a Super Artifacts page naming the account this would publish to. Allow it and Junie holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Warp ```prompt Connect Super Artifacts to Warp, 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 — Settings → Agents → MCP Servers → Add (or Warp Drive → Personal → MCP Servers), and enter this URL as a Server-Sent Events / Streamable HTTP server. { "super-artifacts": { "url": "https://pr-767-stg.superartifacts.app/mcp" } } 2. Connect over OAuth — Warp offers a one-click Connect for servers that support OAuth, which this one does — approve it and your browser opens a Super Artifacts page naming the account this would publish to. Allow it and Warp holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Qwen Code ```prompt Connect Super Artifacts to Qwen 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 — Paste this into .qwen/settings.json for one project, or ~/.qwen/settings.json to make it global. Qwen Code discovers the OAuth endpoints from the server itself. { "mcpServers": { "super-artifacts": { "httpUrl": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Open the /mcp dialog and authenticate super-artifacts. Your browser opens a Super Artifacts page naming the account this would publish to; allow it and Qwen Code holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Kilo Code ```prompt Connect Super Artifacts to Kilo 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 — Paste this into kilo.jsonc at the project root (or ~/.config/kilo/kilo.jsonc to make it global). { "mcp": { "super-artifacts": { "type": "remote", "url": "https://pr-767-stg.superartifacts.app/mcp" } } } 2. Connect over OAuth — Kilo Code starts the OAuth flow automatically on first connection — your browser opens a Super Artifacts page naming the account this would publish to. Allow it and Kilo Code holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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. ``` ### Manus ```prompt Connect Super Artifacts to Manus, 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 custom MCP server — Settings → Integrations → Custom MCP Servers → Add Server. Manus's cloud calls this address directly, so it has to be a public URL — which this is. Name it and paste the URL; Manus verifies it can reach the server and lists its tools before the integration goes live. https://pr-767-stg.superartifacts.app/mcp 2. Then connect it over OAuth — Manus asks for the credential the server requires when it first calls a tool — this server's answer to that is the same OAuth challenge every entry here uses. A Super Artifacts page names the account this would publish to; allow it and Manus holds its own key, revocable from the agents page. Connecting publishes nothing. Server URL: https://pr-767-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-767-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 ." 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`. **Check the connection.** The agent names its account and environment without publishing. ```prompt 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](https://pr-767-stg.superartifacts.app/screenshots/docs/connect-create-key-light.0012483d.webp) *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](https://superartifacts.app/agents). A connection by itself publishes nothing. Next: [Create artifacts](https://pr-767-stg.superartifacts.app/docs/create.md).