Integrations

Supabase

Connect Supabase to query and change your database, run migrations, manage users, files and Edge Functions, and check logs and advisors.

API credentialsDeveloper & InfrastructureSupabase API docsSupabase MCP server overview

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.

Setup time
1 min
Auth
API credentials
API base URL
https://api.supabase.com
Rate limits
120 requests a minute per user, per project or organization, per endpoint; logs and usage analytics 30 a minute; database context 10 a minute (Supabase Management API introduction). Responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset; over a limit Supabase answers 429 for the rest of the minute.

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

Open Access Tokens in your account

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

Open this screen →

supabase.com/dashboard/account/tokens
Ada Dev
Account settings / Access Tokens

Access Tokens

Tokens let tools use the Supabase Management API as you.

Generate new token

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.

Open this screen →

supabase.com/dashboard/account/tokens
Ada Dev
Account settings / Access Tokens

Access Tokens

Tokens let tools use the Supabase Management API as you.

Generate new token
Name
PopMCP
Organizations and projects
Acme
Permissions
Read and write
CancelGenerate token

Copy the token

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

Open this screen →

supabase.com/dashboard/account/tokens
Ada Dev
Account settings / Access Tokens

Access Tokens

Tokens let tools use the Supabase Management API as you.

Copy your token now. You will not be able to see it again.
PopMCP
Token
sbp_8f31****************************c7a9
Copy

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.

Connect in PopMCP

Open your workspace, choose Supabase in the marketplace, and fill in the connect dialog:

FieldWhat to enter
Access tokensecretIn 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.Encrypted with AES-256-GCM on save and never shown again.

PopMCP verifies the credential against Supabase immediately. On success the connection flips to Verified and its MCP tools are provisioned.

Verify it worked

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..."

Why: 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..."

Why: 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..."

Why: 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

Why: 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

Why: 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..."

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

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

Reference

On this page