Connect

Every client connects to the same address and signs in the same way: you approve once in your browser with your Supercurve account. There are no API keys to copy.

Once connected, ask the app: "Which websites can you see in Supercurve?" The answer lists your sites, which confirms the connection end to end.

ClaudeCopy Anchor Link

Claude on the web and desktop. Custom connectors need a Pro, Max, Team or Enterprise plan.

1. Open Claude. Go to Settings, then Connectors, and choose Add custom connector.
2. Add the Supercurve URL. Paste https://mcp.supercurve.ai/mcp as the connector URL and save. Claude finds the sign-in on its own.
3. Sign in with Supercurve. Click Connect, then choose Allow in your browser. Back in Claude, turn Supercurve on in the tools menu and ask away.

On Claude Team and Enterprise, an Owner adds Supercurve under Organization settings, then Connectors, first. Members then connect with their own Supercurve account from Customize, then Connectors.

Claude CodeCopy Anchor Link

1. Add the server. Run this once in your terminal. It registers Supercurve as a remote MCP server for Claude Code.

   Copy Text

   claude mcp add --transport http supercurve https://mcp.supercurve.ai/mcp

2. Sign in. Inside Claude Code, type /mcp and pick Supercurve to start the sign-in. Choose Allow in your browser.

Claude Code uses a loopback address on your machine for the sign-in return; the consent page shows it so you can check it is yours.

ChatGPTCopy Anchor Link

Custom MCP servers are available on Plus, Pro, Business, Enterprise and Education plans.

1. Turn on Developer mode, then add a custom MCP. In ChatGPT, open Settings, then Security and login, and turn on Developer mode. Then go to Plugins, then MCPs, choose Add, then Connect to a custom MCP. Name it Supercurve and set the type to Streamable HTTP.
2. Add the Supercurve URL. Paste https://mcp.supercurve.ai/mcp as the URL and save. Saving does not start the sign-in yet; that is the next step.
3. Sign in with Supercurve. Back in the MCPs list, open Supercurve and choose Authenticate. Choose Allow in your browser, then turn Supercurve on in a chat. ChatGPT asks before any action that changes something.

CodexCopy Anchor Link

The same setup works in the Codex CLI, the IDE extension and the app.

1. Add the server. Run this once in your terminal.

   Copy Text

   codex mcp add supercurve --url https://mcp.supercurve.ai/mcp

2. Sign in. This opens the Supercurve sign-in in your browser. Choose Allow once.

   Copy Text

   codex mcp login supercurve

Longer questions can pass the default 60 second tool timeout. In ~/.codex/config.toml, under [mcp_servers.supercurve], set tool_timeout_sec = 90.

MuseCopy Anchor Link

Muse builds the connector itself from a chat message. Use muse.ai in a browser on a computer; the phone app cannot finish the sign-in yet.

1. Open Muse on a computer and send it this message:

   Copy Text

   Add Supercurve as a custom connector. It is a remote MCP server at https://mcp.supercurve.ai/mcp. It signs in with OAuth, so open the sign-in in your browser for me to approve.

2. Sign in when Muse hands you the browser. Muse opens the Supercurve sign-in in its own browser and passes it to you. Sign in with your Supercurve account and choose Allow.

3. Ask away. Muse keeps the connector and asks before any action that changes something. If it says its browser is down, you are probably in the phone app: switch to muse.ai on a computer.

Muse CodeCopy Anchor Link

1. Add the server. In ~/.config/muse/settings.json, add Supercurve under mcp_servers. Keep the file's schema_version line; without it Muse Code refuses to start.

   Copy Text

   {
     "schema_version": 1,
     "mcp_servers": {
       "supercurve": {
         "type": "streamable_http",
         "url": "https://mcp.supercurve.ai/mcp"
       }
     }
   }

2. Sign in. This opens the Supercurve sign-in in your browser. Tokens live in Muse Code's auth store and refresh on their own; a 401 mid-session prints this same command.

   Copy Text

   muse mcp login supercurve

3. Choose Allow once. Back in Muse Code, /mcp lists Supercurve and its tools.

OpenClawCopy Anchor Link

1. Add the server. Run this once. OpenClaw stores it under mcp.servers in its config.

   Copy Text

   openclaw mcp add supercurve --url https://mcp.supercurve.ai/mcp --transport streamable-http --auth oauth

2. Sign in. Follow the printed authorization URL. OpenClaw captures the loopback redirect and saves the credentials itself.

   Copy Text

   openclaw mcp login supercurve

3. Choose Allow once, then reload or restart the gateway so it picks up the new server. openclaw mcp doctor supercurve --probe checks the connection.

Hermes AgentCopy Anchor Link

1. Add the server. In ~/.hermes/config.yaml, add Supercurve under mcp_servers. In a running session, /reload-mcp picks it up.

   Copy Text

   mcp_servers:
     supercurve:
       transport: streamable_http
       url: "https://mcp.supercurve.ai/mcp"
       auth: oauth

2. Sign in. This opens the Supercurve sign-in in your browser. Tokens are kept in ~/.hermes/mcp-tokens and refresh on their own.

   Copy Text

   hermes mcp login supercurve

Hermes has an open issue where OAuth servers connect but register no tools in the agent loop (hermes-agent issue 39551). Check with hermes mcp test supercurve first.

Any other MCP clientCopy Anchor Link

Any client that speaks MCP over Streamable HTTP and supports OAuth with dynamic client registration can connect to https://mcp.supercurve.ai/mcp. The security page describes the discovery flow in detail.

DisconnectCopy Anchor Link

To stop an app, remove the connector in that app. Its access ends when the current token expires, within an hour. Nothing on the Supercurve side needs cleaning up.