An open application backend that combines database, APIs, authentication, storage, realtime, edge functions, an official MCP server, and guidance for deploying customer-owned MCP services.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Query project databases and schemas, manage migrations, deploy Edge Functions and perform supported project-development operations; also provides patterns for deploying custom MCP servers and authenticating them through Supabase Auth
Query project databases and schemas, manage migrations, deploy Edge Functions and perform supported project-development operations; also provides patterns for deploying custom MCP servers and authenticating them through Supabase Auth
Read-only mode is optional. Without read_only=true, documented MCP tools can apply migrations, execute SQL, deploy Edge Functions, create, pause, or restore projects, manage database branches, confirm costs, and update storage configuration. Treat these as consequential development and database writes.
Project scoping and read-only modes are recommended; the self-hosted Studio MCP is internal-only and must not be exposed publicly, while custom Edge Function authentication remains a separate implementation concern. Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary.
Project scoping and read-only modes are recommended; the self-hosted Studio MCP is internal-only and must not be exposed publicly, while custom Edge Function authentication remains a separate implementation concern. Official Supabase documentation identifies the hosted MCP as development tooling for AI coding agents, not a general end-user application surface. Project scoping and read-only modes are recommended; the self-hosted Studio MCP is internal-only and must not be exposed publicly, while custom Edge Function authentication remains a separate implementation concern.
Official Supabase documentation identifies the hosted MCP as development tooling for AI coding agents, not a general end-user application surface. Project scoping and read-only modes are recommended; the self-hosted Studio MCP is internal-only and must not be exposed publicly, while custom Edge Function authentication remains a separate implementation concern.
First-party MCP tool catalog
The exact feature-group tool names published for Supabase's hosted and local development MCP server configurations. Reviewed Jul 10, 2026. The available catalog changes with project_ref, read_only, and feature selections. Storage tools are disabled by default, Branching is experimental and paid-plan dependent, and project scoping removes account-management tools. Supabase warns against connecting this development-oriented server to production data.
list_tablesreadlist_extensionsreadlist_migrationsreadapply_migrationconsequential writeexecute_sqlconsequential writeget_logsreadget_advisorsreadget_project_urlreadget_publishable_keysreadgenerate_typescript_typesreadlist_edge_functionsreadget_edge_functionreaddeploy_edge_functionconsequential writelist_projectsreadget_projectreadcreate_projectconsequential writepause_projectconsequential writerestore_projectconsequential writelist_organizationsreadget_organizationreadget_costreadconfirm_costwritesearch_docsreadcreate_branchconsequential writelist_branchesreaddelete_branchconsequential writemerge_branchconsequential writereset_branchconsequential writerebase_branchconsequential writelist_storage_bucketsreadget_storage_configreadupdate_storage_configconsequential writeTry a broader name, group, action, or availability term.
First-party access
Agent access
Role: provider
Read scope: Query project databases and schemas, manage migrations, deploy Edge Functions and perform supported project-development operations; also provides patterns for deploying custom MCP servers and authenticating them through Supabase Auth
Write scope: 13 of 32 reviewed named tools have a write, draft, or mixed action label, including apply_migration, execute_sql, deploy_edge_function, create_project, pause_project, and others. Read each catalog boundary before enabling them.
Authentication: Project scoping and read-only modes are recommended; the self-hosted Studio MCP is internal-only and must not be exposed publicly, while custom Edge Function authentication remains a separate implementation concern.
Approval boundary: Project scoping and read-only modes are recommended; the self-hosted Studio MCP is internal-only and must not be exposed publicly, while custom Edge Function authentication remains a separate implementation concern.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed interfaces
These are design proposals derived from documented access—not claims that Supabase ships these experiences.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Official Supabase documentation identifies the hosted MCP as development tooling for AI coding agents, not a general end-user application surface. Project scoping and read-only modes are recommended; the self-hosted…
Targeted first-party MCP/agent-role review; broader API inventory retained
Platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party agent and MCP overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party guide to deploying customer-owned MCP servers.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party platform documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party API documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party event, extension, or embedding documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to the representative first-party source or targeted access review.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.