Keys / Supabase

SUPABASE_ACCESS_TOKEN

A personal access token for the Supabase Management API, the Supabase CLI and the Supabase MCP server.

Starts with
sbp_
Expires
you choose
API
none in the Management API; dashboard only

Get it

Create one on supabase.com/dashboard/account/tokens. The steps aren't recorded yet.

Set it

SUPABASE_ACCESS_TOKEN=sbp_...

The Supabase CLI and the Supabase MCP server read it on their own. The CLI prefers it over a token saved by supabase login. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. On the Access Tokens page, create a new token with the same organizations, projects and permissions as the old one.
  2. Deploy it everywhere that reads SUPABASE_ACCESS_TOKEN, such as CI.
  3. Check that nothing still uses the old token, then delete it.

Set rotate_every on the key in keypin.toml and a rotated date on its vault item, and keypin status shows when it's due.

Sources, checked 2026-11-16