API keys
Let coding agents and scripts read your saved stacks and save new ones.
An API key lets a coding agent or a script work with one organization's saved stacks. It acts as you, in that organization only. It can never do more than you can as a member, and it stops working if you leave the organization.
Make a key
Console path: User menu → API keys, at /settings/api-keys.
- Select New API key.
- Name the key after where it will live, such as "Claude Code on my laptop".
- Choose the organization.
- Choose the access:
- Read stacks: list the organization's stacks, their health and the changes they haven't seen.
- Read and save stacks: also save stacks the planner chooses, as you.
- Choose when it expires: 30 days, 90 days, 1 year or never.
- Select Create key and copy it. Clearvia shows the key once and keeps only a hash of it.
Renaming, re-planning, marking changes as seen and deleting stacks stay in the console. A key can't make or revoke keys.
Use a key
Send the key as a bearer token. To connect Claude Code to the MCP server with your stacks:
claude mcp add --transport http clearvia https://api.clearvia.app/mcp \
--header "Authorization: Bearer $CLEARVIA_API_KEY"The REST API takes the same header.
Revoke a key
Open the key's ⋯ menu and select Revoke. The key stops working at once. A key that expired keeps its place in the list until you revoke it, so you can see why an agent stopped.
Keep keys safe
- Keep keys in your agent's configuration or a secret manager, never in a repository.
- Give each agent or script its own key, so you can revoke one without the others.
- Choose Read stacks unless the agent should save stacks.
- An account holds up to 20 keys.
Next
Save a stack or connect the MCP server.