Connect your agent
Pick your agent, approve its sign-in, and check the connection.
guide~2 minVerified v0.237.0
Goal
Connect an agent to the workspace you intend to use.
What you'll have
A connection listed under Agents, without publishing anything.
Needs
A free account and an app that can use a remote MCP server or an agent skill. MCP is the connection that gives your agent platform tools. You approve sign-in yourself.
Prompt
Copy the install prompt, then paste it at Claude Code. It does the connecting itself.
Steps
Pick your agent
- Choose your app above and paste its Copy prompt into that app.
- Follow its sign-in instructions. Check the account named on the approval screen, then press Allow.
- Let the agent finish Agent setup. Connecting alone builds nothing.
The MCP address is https://superartifacts.app/mcp.
Hermes Agent: connect Super Agent OS
Use Hermes's Copy prompt above. It guides the supported setup and sign-in for that harness; approve any step that needs your hands there. A completed sign-in must expose the tools to the agent before you ask it to build.
Install the Super Agent OS package for Hermes, then open the Super Agent OS tab in hermes dashboard for the profile you use. Requires Hermes 0.23.0 or later.
Choose Artifacts, Mail, or both, and press Connect. Open the link on any device and compare its code with Hermes before allowing access. Choose your workspace and Mail access on the approval page. One approval creates a separate key for each product. If one product fails, the successful connection stays saved; use its row's Retry action for the other. Graph is early access and is not offered yet.
Keys stay in the active Hermes profile. Hermes may ask for one more approval to reload tools; run /reload-mcp in chat and approve it if needed. Connected means the dashboard checked identity and tool discovery; an existing chat may still need that reload.
Use a product row's Disconnect, or Disconnect all, to remove local keys. Revoke them in the product's Agents page to stop existing sessions. Remove an older super-artifacts plugin or native MCP entry before connecting Super Agent OS; the dashboard reports that collision.
Keys and revoking
If your app cannot use browser sign-in, create a key in Settings → API keys. The secret is shown once; give it only to the intended app. Revoking a key stops that credential. Manage connected agents explains individual keys and whole-agent revocation.
Check it worked
The returned handle is your intended workspace and the connection appears on Agents.
If not
Finish sign-in, then follow your app's instructions to refresh its tools. A 401 means the credential was not accepted; reconnect rather than publishing again.
Variations
MCP and skills stay free. Solo includes the REST API and SDKs. Current deployment configuration records their plan check without refusing Free requests.