Supabase announced a code-first workflow, app MCP servers and safeguards for agents at Select 2026

Archive entry: this covers an event from October 2, 2026, and we published it on November 8, 2026. The details come from sources dated at the time and may have changed since.

On October 2, 2026, Supabase announced a code-first workflow for coding agents at Supabase Select, according to the Supabase Select 2026 recap. Supabase said it worked code first: schema and config could live in code, so a coding agent could set up and change a project the same way a developer does.

What Supabase announced

• Local development: Supabase could run locally as native processes without Docker (alpha, off by default), and several local instances could run at once, one per directory.
• Declarative Schemas 2.0 generated migrations from SQL schema files with pg-delta, and dashboard changes could be pulled back into files with supabase config pull.
• An MCP server for each app let the app's users connect their own agents. It ran as an Edge Function, users signed in through the app's existing Auth, and RLS policies decided what each tool call could reach.
• Supabase Compute, for running web services and agents in any language next to the database, was announced in private alpha with a waitlist.
• Supabase also announced Multigres, multi-node high availability for Postgres, in private alpha, and OrioleDB in public beta.

What it meant for people who build with AI

The backend many AI builders used was being rebuilt so agents could configure and operate it, with guardrails on destructive actions. Because schema and config could live in code, an agent could change a project the way a developer would, and the app MCP server let an app's own users bring their own agents under the app's Auth and RLS rules.

Safeguards for agent access

The Supabase MCP server asked for confirmation before an agent created a paid project or branch or ran SQL that could delete data, and these confirmation prompts (elicitations) were on by default. Enterprise-Managed Auth for the Supabase MCP server, starting with Okta, and scoped personal access tokens were generally available.

Sources

• Supabase Select 2026 Recap (Supabase, October 2, 2026, official)

Written with AI assistance, strictly from the sources listed above. Before it went live, automated checks verified its dates, sources and every language edition.