# Supabase setup for PopMCP

You paste one value into PopMCP: an access token from your Supabase account. You then choose a whole organization, or one project, for the connection.

- Auth: API credentials
- Setup time: 1 min
- API base URL: https://api.supabase.com
- Credentials screen: https://supabase.com/dashboard/account/tokens
- Provider docs: https://supabase.com/docs/guides/platform/personal-access-tokens

## Before you begin

- A Supabase login. Access tokens are free on every plan, including Free
- To make changes, an organization role that allows them. A token can never do more than your own role allows
- To reach a project's users, files and rows, a role of Owner, Administrator or Developer, because those tools use the project's secret key

## Get your credentials

### 1. Open Access Tokens in your account

Sign in at supabase.com and open your account's Access Tokens page. Choose Generate new token.

Screen: https://supabase.com/dashboard/account/tokens

### 2. Name the token and choose what it can reach

Give it a name such as PopMCP. Supabase scopes tokens by default: choose the organizations or projects it may use and the permissions it gets. For every tool, give it read and write on them, plus Read on Organizations and Projects (account-wide) so PopMCP can list them. To also reach users, files and rows, include API Keys and API Key Secrets. A token with full access works too, and shows a Legacy badge in the list.

Screen: https://supabase.com/dashboard/account/tokens

### 3. Copy the token

Supabase shows the token once. It starts with sbp_. Copy it now: you cannot see it again later.

Screen: https://supabase.com/dashboard/account/tokens

### 4. Paste the token into PopMCP and choose what to connect

In PopMCP, paste the token into Access token and connect. PopMCP lists your organizations and their projects. Choose All projects in an organization, or one project to keep the connection to that project and its branches. Each choice goes into its own workspace.

## Fields PopMCP asks for

- Access token (accessToken) [required]: In Supabase: open your account, Access Tokens, and generate a new token. Name it, and either give it full access or pick the organizations, projects and permissions it may use. Copy it right away: Supabase shows it once. Stored encrypted.

## Verify

PopMCP marks the Supabase connection Verified with the project's or organization's name and records the region, status or plan. Asking the AI to list your tables returns them with row estimates and whether Row Level Security is on.

## Troubleshooting

### "That is one of a project's API keys..."

Cause: You copied a key from a project's API Keys page. PopMCP needs a token from your account.

Fix: Open your account's **Access Tokens** page and generate a token. It starts with **sbp_**.

### "Supabase did not accept this token..."

Cause: It expired on the date chosen when it was made, it was deleted, or it was copied incompletely.

Fix: Generate a new token under **Access Tokens** and connect again.

### "This token cannot list your organizations and projects..."

Cause: The token was scoped without Read on **Organizations** and **Projects (account-wide)**.

Fix: Generate a new token with those two permissions added.

### A tool says it needs the project's secret key

Cause: The token lacks **API Keys** and **API Key Secrets** read, or your organization role cannot read them.

Fix: Generate a token with those permissions, or ask an owner for a role that has them. SQL tools keep working without it.

### A tool answers that the project is paused

Cause: Free projects pause after a period without use, and a paused project's database cannot be reached.

Fix: Ask the AI to restore the project, or restore it in the Supabase dashboard, then try again.

### "...is outside this connection..."

Cause: The AI named a project you did not choose when you connected.

Fix: Connect that project or its organization too, in its own workspace.

---

Source: https://www.docs.popmcp.com/docs/integrations/supabase/