Skip to main content
Supernova gives AI agents the tools to take any action on your users’ online accounts, both actions that require user authentication and those that don’t, such as searching for products, building a cart, and checking out. Your agent connects to the Supernova MCP server with an MCP token you create for each user. For actions requiring authentication, users link their accounts once and your agent can then take those actions.
Supernova is in early access and runs in production only. Join the waitlist to get access.

Connection details

An MCP token acts as the one user you created it for. The agent can reach only that user’s accounts and the sites enabled for your Knot account.
1

Get your API key

In the Knot Dashboard, retrieve your client_id and secret and base64 encode them to create your API key. Docs here for further details.
2

Create an MCP token for a user

From your backend, call Create MCP Token with your client_id and secret as Basic auth. Supernova can perform both unauthenticated and authenticated (i.e. behind a login) actions online. To enable authenticated actions (recommended), providing the user’s phone_number when creating the MCP token is required, so the Supernova MCP can create sign-in links.
Request
Response
The token acts for that one user. Keep your client_id and secret on your backend and give your agent only the MCP token. Tokens last 1 day by default and up to 30 days. Call Revoke MCP Tokens to revoke all of a user’s tokens.
3

Add the Supernova MCP to your agent

Point your MCP client at https://supernova-mcp.knotapi.com/mcp over Streamable HTTP and send the MCP token in the Authorization header as Bearer sn_prod_....

Try it locally

The fastest way to try Supernova is to add it to a coding agent on your machine. Save your API key to your shell:
Save your API key
Then paste this prompt into your coding agent. It asks for your phone number, creates an MCP token, saves it to your shell, and adds the server:
Setup prompt
Or set SUPERNOVA_MCP_TOKEN to a token from step 2 and add the server yourself:

Add it to your deployment env

When you’re ready, connect the Supernova MCP to your user-facing agent, from the server where it runs. Your backend creates an MCP token for each user and passes it to your agent’s MCP client. Create the token when the user starts a conversation, reuse it until its expires_at, and never send it to your client app.
The MCP connector connects Claude to Supernova from the Messages API:
4

Interact with Supernova in your agent

Ask your agent to do something on a site, such as “Find me some tasty ice cream.” If the action requires authentication to an online account and an account is not linked, your agent gets a sign-in link from the Supernova MCP and will return it to you to sign-in.

Linking online accounts

Some actions need the user’s own account at a site. The agent calls supernova_list_accounts and supernova_link_account to check whether the user has a linked account there. If not, it gets a sign-in link and returns it to the user in the UI, the user confirms a code texted to their phone, and signs in to the site. The agent never asks for the user’s username or password to the site. OTP codes are texted to the phone number provided in Create MCP Token.

Running actions

The agent sends the user’s request to supernova_do in plain language. Supernova routes it to the right action, runs it, and returns only the fields the request needs. Some sites also support guest actions, such as searching without signing in. The agent creates a guest session with supernova_create_guest_session and passes its ID as session.