Access Tokens let external tools reach your Vibgrate data securely. Create a token to connect the Vibgrate CLI or an MCP client — like Claude or Cursor — to your workspace, scoped to exactly the access you intend.
What you'll see
- Tokens — the access tokens you've created, with their scope and last use.
- Scopes — whether each token can read only, or read and write.
- Workspace binding — which workspace each token can reach.
Create a token
- Open Settings, then Access tokens.
- Select New token.
- Choose the workspace and the scope (read, or read and write).
- Copy the token when it's shown — you won't be able to see it again.
Keeping tokens safe
Grant the narrowest scope that does the job — read-only for anything that only needs to query data. Treat a token like a password: store it somewhere safe, never commit it to code, and revoke it here the moment it's no longer needed or might be exposed. Vibgrate only stores a hash of each token, so it can verify a token without ever being able to show it again.
Tokens and the dashboard chatbot
You don't need a token for the Ask Vibgrate (Pulse) chatbot inside the dashboard — that runs on your signed-in session. Tokens are for connecting outside tools.