Supabase from Code Moves Backend Setup Into Repositories.

Supabase from code lets coding agents define backend infrastructure inside the same repository as the application. Supabase also announced app-specific MCP servers and long-running services on Supabase Compute.

The Supabase Select announcement describes a shift away from backend changes that only happen in the dashboard. Agents can now work on schemas and project configuration alongside the rest of the application code.

An agent can write the database schema as SQL files. pg-delta then works out the migration required to apply those files.

Project settings can move in both directions. Changes made in the dashboard can be brought back into the project’s configuration file with one command, keeping the repository aligned with the hosted project.

Local development no longer requires Docker. Each directory gets its own local stack, so an agent can test two changes side by side before choosing which one to keep.

This gives coding agents access to work that previously required a person to create tables, edit row-level security policies in the dashboard and pull those changes into migrations through the CLI.

Supabase projects can now host an MCP server for the app itself. This gives users’ agents a standard route into the application from tools such as Claude, ChatGPT and Cursor.

Users sign in through the app’s existing authentication flow. Their agent then sees only the data and actions that user is permitted to access. The MCP server is deployed inside the same Supabase project as the app.

This app-facing server follows Supabase’s work on enterprise-managed authentication for its MCP server.

Supabase Compute covers work that cannot finish inside a short request. It runs long-lived services in the same project as the database. Examples in the announcement include agents, generating embeddings for large sets of files, persistent services and code that needs its own sandbox.

Together, the three additions cover the agent workflow from backend creation to app access: an agent can configure the backend from code, Supabase Compute can run persistent jobs, and users’ agents can enter the finished app through its MCP server.

What is Supabase from code?

Supabase from code is a workflow for defining a project’s schema and configuration inside an application repository. Coding agents can write SQL schema files, generate migrations through pg-delta and test changes using local stacks.

How does Supabase from code handle migrations?

The agent writes the intended schema as SQL files. pg-delta compares the schema and works out the migration needed to apply the change.

Which Supabase plans include these features?

The announcement does not list plan or pricing details for these features. It describes Supabase from code, app MCP servers and Supabase Compute as tools announced at Supabase Select on 2 October 2026.