Skip to content

Supabase

Manage the database and sign-in services behind your app.

View Markdown

Connect Supabase#

Keep a working native login, or save the keys below.

Shell
godmode setup supabase

Account access#

The legacy full-access personal token reaches all organizations and projects your account can access, including future ones. Scoped tokens are also available. This credential authenticates the Management API, CLI and compatible tools; it is not a database password, project publishable key or runtime secret key.

Add credentials#

Save only the keys your product needs.

Access token#

Manage your Supabase projects through the CLI and Management API.

Visit Supabase's access tokens

  1. Select Generate new token > Create legacy token.
  2. Type a name and set Expires in to Never.
  3. Select Generate token, then copy the token.

Save as SUPABASE_ACCESS_TOKEN in Godmode.

Check access#

  • List accessible organizations and projects through the Management API or official CLI, then confirm the intended project and account role. Use the relevant management permissions for project configuration, database work and deployments. Check the installed CLI help: hosted and local targeting can differ by version.

Restore access#

  • Check account role and token scope on permission errors. Replace an expired or revoked token in account settings and save it with godmode set SUPABASE_ACCESS_TOKEN. The CLI reads this environment variable before a saved login token; Godmode does not update the CLI cache.

Provider docs#

Source: Godmode v0.20.0 provider catalog · 2026-11-13.

Godmode v0.20.0 · 2026-11-19 · Inspect the source · Get help