Supabase

Manage Supabase projects and development workflows through Supabase’s hosted MCP server.

See the official Supabase MCP documentation for setup, configuration options, and security guidance.

Access mode: Enter true for read-only access or false to enable potentially destructive read-and-write operations.

What you’ll need to connect

Choose whether to restrict the connection to read-only operations. Read-only access is recommended unless you need to apply migrations, deploy functions, or manage projects and branches.

Authentication uses OAuth with dynamic client registration by default. You can instead provide a Supabase personal access token for non-interactive access. When a token is provided, Supabase authenticates directly with it and does not start OAuth; when omitted, Obot uses OAuth.

Security

• Use a development project or branch with non-production data. Never connect this server to production data.
• Review every tool call before approving it, especially SQL, migrations, deployments, and project or branch operations.

Features

• Database: Inspect schemas and migrations, execute SQL, and optionally apply migrations
• Debugging: Retrieve logs and security or performance advisors
• Development: Get project URLs and publishable keys, and generate TypeScript types
• Edge Functions and Branching: Inspect functions and branches, with optional write operations
• Storage and Docs: Inspect storage configuration and search Supabase documentation

⚠️ Upgrade notice

If you’re upgrading this server, note that this replaces the Obot-hosted Supabase server with Supabase’s official hosted MCP server.

• Reconnect required: Select read-only or read-and-write access, then connect with OAuth or optionally provide a Supabase personal access token.
• Authentication change: A personal access token is no longer required; OAuth is used when the token is omitted.
• Tool changes: Tool names, parameters, and available project, database, function, branch, storage, and documentation operations change.