From the source
- Expo built a
Supabase integration into the EAS CLI so developers can create a Supabase project, install the SDK and write keys to every Expo environment with one command.
- The command, eas integrations:supabase:connect, replaces the old routine of creating a project in one dashboard, copying keys into another and checking that preview and production held the right values.
- Adding --environment preview gives Preview its own Supabase project with separate keys, leaving production data untouched, while Development can point at a local Supabase stack.
- Supabase Security and Performance Advisors run from the CLI and report findings such as a table with Row Level Security disabled or a foreign key without an index in the Expo build dashboard, next to the build logs for the change that introduced it.
- Every command runs without prompts and returns JSON, so an agent scaffolding an app can set up its backend in the same pass.
- Quilia, which builds a client app for personal injury law firms, uses a read-only Supabase MCP server and a development project to ship several fixes a day through Expo Update.
- The integration requires eas-cli 21.8.0 or newer and a project linked to Expo.






