SquidX logo
Open SquidX

Claude Code

No key to paste: your browser opens, you sign in, and you choose an access level: read only, read and write, or custom.

No key to paste: your browser opens, you sign in, and you choose an access level: read only, read and write, or custom.

Scope: Only you, in the current project.

  1. 1

    Add the server

    One command, from any directory. The scope decides who gets the server.

    bash
    claude mcp add --transport http squidx https://squidx.io/api/mcp

    --transport http matters: without it the command assumes a local process, not a remote server.

  2. 2

    Sign in when asked

    Run /mcp inside Claude Code, pick squidx, and follow the steps in your browser. From a shell, claude mcp login squidx starts the same flow.

Or use an API key

Skip the browser: pass the key as a header when you add the server.

bash
claude mcp add --transport http squidx https://squidx.io/api/mcp --header "Authorization: Bearer sqx_your_key"

Check it worked

bash
claude mcp list

Or ask the assistant something only your workspace can answer: "What is in my SquidX queue this week?" If it cannot connect, claude mcp get squidx reports why, and claude mcp remove squidx undoes the setup.

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