Skip to main content

Supabase

Manage Supabase projects and query a project's API with a management token and project key.

Connect it with: API key. Supabase's own documentation: https://supabase.com/docs/reference/api/introduction.

What agents can do​

Connect Supabase so the agents working your tasks can reach it. With it connected, they can:

  • List your Supabase projects and read a project's settings, health and logs.
  • Run database migrations or read the schema through the Management API.
  • Deploy or read Edge Functions and manage secrets for a project.
  • Query or update the project's tables and storage with the project secret key, when you add one.

Before you start​

  • A Supabase account that is a member of the organization owning the projects.
  • Permission in that organization to do what agents should do (Developer, Administrator or Owner).
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Supabase​

Jaah connects to Supabase with an API key, not with a sign-in button.

Connect with an API key​

Find each value first:

  • Personal access token: Supabase dashboard > your avatar > Account preferences > Access Tokens (supabase.com/dashboard/account/tokens) > Generate new token: name it Jaah, choose its permissions (Projects read at least), then copy it - Supabase shows it once.
  • Project ref (optional): Optional: the project agents work on. Supabase dashboard > the project > Project Settings > General > Project ID (also the first part of the project's address, https://your-ref.supabase.co).
  • Project secret key (optional): Optional: for agents to call the project's own Data and Storage APIs. Supabase dashboard > the project > Project Settings > API Keys > Secret keys > copy (or the legacy service_role key). It bypasses Row Level Security, so give it only to agents you trust with all data.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Supabase card.
  2. Name the secret and choose who can use it.
  3. Fill in Personal access token, Project ref, Project secret key.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Supabase with an API key, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Supabase's API once (GET https://api.supabase.com/v1/projects) with the stored values, and shows whether Supabase accepted it, or which value Supabase refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: access_token, project_ref, secret_key.

Tell the agent in your task description which secret to use, for example “use the Supabase secret org/supabase”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Supabase once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Supabase's side too, revoke or delete the key at Supabase.

Limitations​

  • The access token acts as you across every organization you belong to, within the permissions you gave it; create a scoped token for least privilege.
  • The project secret key bypasses Row Level Security: anyone holding it reads and writes all of the project's data.
  • This connects agents to the Supabase APIs. It does not make Supabase the backend of a Jaah project.
  • The Management API is rate-limited per token (about 120 requests a minute).
  • Agents can do only what the connected Supabase account allows.

Troubleshooting​

Test says Supabase rejected the personal access token (401)

The token was revoked, expired or mistyped. Generate a new one under Account preferences > Access Tokens and select Replace.

Test says Supabase rejected the token (403)

The token's permissions do not include reading projects. Generate a token with Projects read.

Agents get 401 from the project's REST API

The Project secret key is missing or rotated. Copy the current secret key from Project Settings > API Keys and select Replace.

Still stuck? Select Test and read the result: it names the value Supabase refused and the status it answered.

FAQ​

Which key goes where?

The personal access token (sbp_) drives the Management API at api.supabase.com. The project secret key (sb_secret_) drives one project's own API at https://your-ref.supabase.co.

Can I use the publishable or anon key?

Agents can, but it only reaches what Row Level Security allows the public role; Jaah does not ask for it.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Supabase account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.