Skip to main content
An access token lets a client call Corvic without an interactive sign-in. Send it on every request:
Open Access Tokens ↗
Assistants that support sign-in (Claude, ChatGPT, Grok, Muse, Cursor, VS Code) don’t need a token: they sign you in with Corvic instead. Use a token for scripts, backends, agent frameworks, or any client that only accepts headers.

​
Which token to use

Pick the narrowest token that does the job. A room token is the right choice for an integration that only needs one room.
The API keys on Settings → Models → Use via API are for the model gateway only. They can’t call MCP tools.

​
Create an organization token

1

Open Access Tokens

Go to Settings → Access Tokens and choose Create Access Token.
2

Describe it and set an expiry

Add a Description that says where the token will be used, such as Nightly sync from data warehouse, and choose how long it lasts.
3

Copy it now

The token is shown once. Store it in a secrets manager or an environment variable such as CORVIC_TOKEN.

​
Create a room token

Open the room’s MCP Playground and choose Create token (or New token), then pick how many days it lasts. The token can reach that room and nothing else.

​
Revoke a token

Every token you create, organization or room, is listed under Settings → Access Tokens with its scope. Select tokens and revoke them; clients using them stop working on their next call.
Treat tokens like passwords. Don’t commit them to source control or paste them into chats. Choose the shortest expiry that works, and revoke tokens you no longer use.