For CI, a server, or a client that can’t open a browser, connect with a personal token instead of a browser sign-in.
Make a token
Make a personal token on your dashboard’s Account page. It starts with kal_ and is shown once, so copy it then. It lasts 90 days unless you choose otherwise, and it acts as you in your own workspaces, at your role or lower.
Use it
Keep the token in an environment variable, such as KOALAFIX_TOKEN, and send it as a bearer header:
claude mcp add --transport http koalafix https://mcp.koalafix.com/mcp --header "Authorization: Bearer $KOALAFIX_TOKEN" codex mcp add koalafix --url https://mcp.koalafix.com/mcp --bearer-token-env-var KOALAFIX_TOKEN
The first command saves the token’s value in Claude Code’s own settings, outside your repository. Never put a token in a file you commit.
Revoke a token
Revoke it on the same Account page. Revoking or expiring a token also ends any tokens made from it.
Good to know
- ChatGPT on the web can’t send a token header, so it always signs in.
- We keep only a hash of each token, so a lost token can’t be shown again. Revoke it and make a new one.
- Never send a token to support. We will never ask for one.
Related
Still stuck? Email support@koalafix.com from the address you sign in with. Support says what to include and when we reply.