Swapotamus support

For account access, website ownership transfers, connection errors or privacy requests, contact our support address.

Include the affected domain and a description of the issue. Never send passwords, access tokens or verification codes.

Authenticate button not opening?

In Codex desktop or the Codex CLI, you can start the same OAuth connection from Terminal. You need the Codex CLI installed on the same computer as your Codex connection.

Open Terminal and run:
```
codex mcp login swapotamus
```
Open the sign-in URL printed in Terminal. If a browser window does not open automatically, copy that URL into your browser’s address bar. Keep Terminal open while connecting.
Sign in with your approved account, review the permissions, and choose Allow connection. Wait for the authentication complete message and the successful login message in Terminal.
Return to Codex and ask: “Which Swapotamus account is connected?” Then try: “Show my Swapotamus websites.” If the existing chat still reports a connection error, reload its MCP connection or restart Codex, then try again.

Swapotamus is not listed as an MCP server

First run codex mcp list. Only if Swapotamus is missing, register the connection:

codex mcp add swapotamus --url https://swapotamus.com/mcp

Follow any sign-in URL it prints. If it does not start sign-in, run codex mcp login swapotamus afterward.

Saved sign-in was rejected or access was disconnected

If signing in again still reports invalid_grant, a rejected refresh token, or revoked access, clear only Swapotamus’s saved login and reconnect:

codex mcp logout swapotamus
codex mcp login swapotamus

This signs the local client out of Swapotamus. Complete the new consent page before trying account requests again.

These Terminal commands connect Codex on your computer. For ChatGPT web, use the plugin’s Connect flow; a Codex login does not connect your ChatGPT web account. Signing in to the Swapotamus website alone also does not connect either client.

Never paste passwords, access tokens, refresh tokens, or the full sign-in or callback URL into a conversation or support message. If you still cannot connect, contact support with the client name and error message.