Keys authenticate external MCP clients and workspace automation against Crank.
Keys are only shown once. Copy and store them securely immediately after creation — Crank stores only a hash. `Last used` updates after successful MCP authentication.
Active keys
3 active · 1 revoked
Name
Key prefix
Scopes
Created
Last used
Status
Scope reference
read
Initialize MCP sessions, ping the server, and list tools for a workspace agent.
write
Execute `tools/call` requests against published agent toolsets.
deploy
Reserved for deploy-scoped automation. Today it also permits MCP read/write flows.
Create API key
A descriptive label to identify the key. Only visible to admins.