Supabase MCP server
Inspect Supabase projects, database structure, and operational logs with Arc0’s tools. SQL reads and writes are separate actions, and a write can permanently change or delete data. Connect through Arc0 to use the actions your identity is allowed to call.
Working with Supabase
Before investigating a database, use supabase.list_organizations and supabase.list_projects to choose the intended project. supabase.get_project confirms its reference, region, and health state without returning connection credentials. supabase.list_schemas and supabase.list_tables inspect database structure through fixed catalog queries, giving an agent real names to use in subsequent SQL.
supabase.run_sql_read executes through the vendor’s read-only database endpoint. Put a LIMIT in the SQL itself: the output row cap only limits returned data locally, not the work performed by the database. Query results can still contain sensitive records. supabase.get_logs uses a separate log-query dialect and a bounded time window; it is not a database SQL endpoint.
For a reviewed data or schema change, supabase.run_sql_write can execute SQL with permanent effects. Errors can follow partial commits, so inspect the database before repeating a failed-looking request. supabase.generate_typescript_types reads schema metadata after a change, while supabase.list_edge_functions inventories deployed function metadata without downloading code, invoking functions, or deploying anything.
Official MCP reference: Supabase documentation.
Agent workflows for Supabase.
Inspect a project
Use supabase.list_projects and supabase.get_project to confirm the reference, region, and health state.
Understand a database schema
Use supabase.list_schemas and supabase.list_tables before writing a query against named tables.
Investigate a bounded question
Use supabase.run_sql_read for a limited database query or supabase.get_logs for a specific operational time window.
Refresh application types
Use supabase.generate_typescript_types after a reviewed schema change to retrieve matching database types.
11 Supabase actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
9Look things up, subject to your permissions.
- supabase.list_organizationsList organizations
Use when selecting an organization accessible to this personal access token. Returns organization identifiers and names; no pagination is exposed by the vendor. Not for organization members.
- supabase.list_projectsList projects
Use when finding accessible project references, regions, and health states before choosing a project. Returns the complete vendor list without database host details. Not for database rows.
- supabase.get_projectGet project
Use when checking a specific project name, region, organization, or health state. Requires its 20-letter project reference. Not for database connection credentials.
- supabase.list_schemasList database schemas
Use when discovering database namespaces before inspecting tables or generating types. Executes a fixed catalog query through the vendor read-only SQL endpoint; returns at most 1000 schemas. Not for table contents.
- supabase.list_tablesList database tables
Use when inspecting tables and views in one database schema before writing SQL. Runs a parameterized catalog SELECT via the read-only endpoint; returns at most 1000 tables. Not for row data.
- supabase.run_sql_readRun read-only SQL
Use when reading schema-qualified SQL as the vendor read-only DB user. Results may expose personal data or secrets. Not for writes; use list_schemas/list_tables for discovery. Add SQL LIMIT; max_rows caps output locally.
- supabase.get_logsGet project logs
Use when investigating logs with ClickHouse SQL over up to 24 hours (last minute if omitted). Results may contain personal data or secrets. Not for database SQL: use run_sql_read. Add SQL LIMIT; max_rows caps output only.
- supabase.list_edge_functionsList Edge Functions
Use when checking deployed function slugs, versions, and states for one project without downloading code or secrets. Not for invoking or deploying functions.
- supabase.generate_typescript_typesGenerate TypeScript types
Use when producing TypeScript database types for selected schemas after a schema change. Reads schema metadata without changing the database. Not for schema migrations.
write
1Create and change things. Allow, or ask the user first.
- supabase.update_project_nameRename project
Use when changing a project display name. Does not change the project reference or database. Read the project afterward to reconcile a lost or timed-out response before retrying. Not for renaming database objects.
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- supabase.run_sql_writeRun destructive SQL
Use when explicitly authorized to change database data or schema. Can permanently delete data; results may expose personal data or secrets. Not for reads: use run_sql_read. Errors may follow partial commits: reconcile before retrying. max_rows caps output only.
Control access to Supabase.
Connect the intended Supabase account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- supabase.update_project_name: require approval
- supabase.run_sql_write: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Supabase connects.
Connect Supabase using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Supabase with your AI client.
Sign in to Arc0 and connect Supabase in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Supabase with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingSupabase with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSupabase with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingSupabase with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSupabase with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingSupabase with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
More developer tools apps.
Supabase and Arc0, answered.
Is there an official Supabase MCP server, and how does Arc0 differ?
Yes. Supabase provides an official MCP server. Arc0’s current tools call the Management API with a PAT and separate read and write SQL actions under Arc0 policies.
Which permissions does Arc0 need for Supabase?
Use a Management API personal access token, preferably scoped to the needed project and permissions. A project service-role key is not accepted by this lane. Classic PAT access inherits the user’s privileges; SQL write access must be considered separately from schema reads.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.
How are credentials stored, refreshed and revoked?
Arc0 stores the PAT encrypted and does not refresh it. Disconnect removes local access. Revoke the PAT in Supabase’s account controls to invalidate it at the provider; reconnect with a replacement when it expires.
What happens with rate limits or errors?
Supabase applies Management API limits and database constraints. Arc0 reports throttling and query failures. A write error can follow partial commits, so reconcile database state before another attempt. Output limits do not limit query execution cost.
What is the availability of these Supabase tools?
These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.
Plug Supabase into your agent.
Supabase MCP server: 11 actions including list organizations, list projects, get project. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Supabase and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Supabase.