My API token no longer works

Short Answer

API tokens can become invalid for several reasons: You manually revoked the token, created a new token (which automatically invalidates the previous one), or your access has changed.

Details

Why does a token become invalid?

Picasi currently allows only one active API token per workspace. As soon as you create a new token, the previous one immediately becomes invalid. This also applies if you manually deleted the token via Settings → API Tokens → Revoke Token.

Additionally: If you’ve changed your plan and the new plan doesn’t include API/MCP functionality, the token will also no longer be usable.

Create a new token:

Open Settings → API Token and click Generate New Token. Copy the token immediately—it will only be displayed in full once. After that, it will only appear masked in the interface.

Update the token in all configuration files:

If you use Claude Code, enter the new token in .mcp.json or in ~/.claude.json under PICASI_API_TOKEN. For other applications: update all locations where the old token was stored.

Tip: If multiple people on your team use the MCP server, you should store the token in a central, secure location—for example, in a password manager or as a shared secret in your development environment.