SquidX logo
Open SquidX

Codex

Add the server, then sign in. The same setup works in the CLI, the IDE extension and the app.

Add the server, then sign in. The same setup works in the CLI, the IDE extension and the app.

  1. 1

    Add the server

    One command, from any directory.

    bash
    codex mcp add squidx --url https://squidx.io/api/mcp
  2. 2

    Sign in

    This opens your browser. Sign in to SquidX and choose what Codex may do. If the sign-in cannot register by itself, add --oauth-client-registration dcr to this command.

    bash
    codex mcp login squidx

Or use an API key

Keep the key in an environment variable and name it in your Codex config.toml.

toml
[mcp_servers.squidx]
url = "https://squidx.io/api/mcp"
bearer_token_env_var = "SQUIDX_API_KEY"

Check it worked

bash
codex mcp list

Type /mcp in Codex to see the active servers, or ask: "What is in my SquidX queue this week?" To stop using the server without deleting it, set enabled = false in its table in config.toml.

Troubleshooting

The client says it could not register with the sign-in service
The discovery documents did not answer. Check that https://squidx.io/.well-known/oauth-authorization-server loads in a browser, then remove the server and add it again.
I get a 401 with an API key
The header is missing or the key is wrong. It is Authorization: Bearer sqx_..., with the space.
The assistant has no write tools
The access is read only. Disconnect the app in Settings, then sign in again with Read and write, or create a key with it, and reconnect so the client fetches the tool list again.
A tool answers inactive
The workspace has no active plan. Drafts still work. Queuing and publishing need a subscription or credits.
Full reference