Supabase CLI
Supabase's official CLI: local stack, database migrations, Edge Functions deploys and type generation from the terminal
- 2,446 ★ on the repository
- Last commit
Broad access
Why this level
- db push changes the cloud database schema
- Deploys Edge Functions code to the cloud
Install
- Works in
Manual install
npm install -D supabaseProject install, run with npx supabase.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- db push changes the cloud database schema
- Deploys Edge Functions code to the cloud
This is third-party code. Review the repository files before installing.
What it does
The CLI runs the full Supabase stack locally: Postgres, Auth, Realtime, Storage, Edge Functions and the APIs. It creates and applies migrations, diffs schemas, resets the local database and pushes changes to a linked cloud project. Edge Functions are created, served locally and deployed from the same project folder. gen types produces TypeScript types from the local or cloud database. For agents the CLI is useful because every project operation is a plain shell command, and the local stack gives a safe sandbox.
Who it is for. For Supabase developers who keep the schema in migrations and want to hand that work to an agent.
Good fit when
- You want the agent to write migrations and test them on a local database
- You need to regenerate TypeScript types after a schema change
- You need to deploy an Edge Function without the dashboard
Not a fit when
- The project is not on Supabase
- You want conversational access to a cloud project without a terminal: the Supabase MCP server covers that
Example request
Create a migration adding a profiles table, apply it to the local database and regenerate typesLimitations
The local stack runs in containers, so Docker or a compatible runtime is required. link and db push work with a Supabase cloud account, which may not be reachable from Russia without a VPN. Container images are pulled from foreign registries.
How to disable. Stop the stack with supabase stop and uninstall the CLI with the same package manager: npm uninstall supabase, brew uninstall supabase or scoop uninstall supabase.
FAQ
How do I link a local project to a cloud one?
Run supabase login, then supabase link. After that db push applies migrations to the cloud database.
Can I install it without Node.js?
Yes, there are Homebrew, Scoop, Linux packages in releases and an install script.
Discussion
No questions or reviews yet.
Related
CLI toolsSupabase's official skills: help an agent work with the database, Auth, Edge Functions and Postgres best practices
Supabase's official MCP server: the agent manages tables, reads project config and queries data after an OAuth login
Two official Prisma MCP servers: a local one for migrations and Prisma Studio, and a remote one for managing Prisma Postgres databases
Instant REST and MCP over PostgreSQL: the agent reads an existing database through an MCP endpoint with no backend to write
A Claude Code plugin for Butterbase: 39 skills and 34 commands take an idea to a deployed app on a hosted backend
A PostgreSQL MCP server with index tuning, EXPLAIN plans, database health checks and a read-only mode
README in short
The README lists install options: a script, npm, Homebrew, Scoop and Linux packages. It then walks through starting the local stack, linking a cloud project, migrations, Edge Functions and type generation. For contributors it describes the monorepo layout and contribution rules. MIT licensed.