Supabase

Explore Supabase developer tools and Agent Skills for building applications with Postgres, authentication, storage, and functions. Understand how the platform, local development workflow, and database guidance support application features and reliable backend changes.

About Supabase

Supabase builds a development platform around Postgres, bringing together database access, authentication, storage, APIs, functions, and realtime features. Its approach gives application developers an integrated backend while keeping the database and surrounding open-source tools visible as distinct technical components.

The ecosystem includes the main platform, client integrations, and a CLI for local development and database workflows. A hosted project provides a managed starting point, while self-hosting and local development offer other operating models. These options share concepts but have different setup and maintenance responsibilities.

The official Supabase Agent Skills repository supplies instructions for working with this ecosystem. The broad supabase Skill addresses product integration and troubleshooting; supabase-postgres-best-practices covers SQL, schema decisions, security, and performance. The Skill repository is MIT-licensed, separate from the licenses of other software components and the terms of hosted services.

Supabase Developer Tools

Explore the Supabase platform and CLI behind application backends and database development. Compare hosted projects, local workflows, migration management, and self-hosting responsibilities to understand where each tool fits in your architecture.

More Teams and Creators

Explore developer tools, software projects, and Agent Skills from other teams and creators. Compare their areas of focus, representative work, and intended tasks to find more resources for development and collaboration.

Supabase FAQ

Is Supabase only a hosted Postgres database?
Postgres is the foundation, but the platform also integrates authentication, storage, APIs, functions, and realtime capabilities. You can use the parts that fit your application.
Which Supabase Skill should I use for a SQL or schema task?
supabase-postgres-best-practices addresses database work including SQL, migrations, indexes, connections, and security. The broader supabase Skill adds platform integration and troubleshooting context.
Does the Postgres Skill apply outside Supabase?
Yes. Its published scope includes Postgres running anywhere, although an application’s actual configuration and workload still determine which recommendations fit.
What is the role of the Supabase CLI?
It supports local development, database migrations, type generation, and function deployment. It is execution tooling; Skills provide instructions for making and checking the surrounding changes.
Does enabling an API replace row-level security?
No. API or table access determines whether a role can reach a resource, while row-level security controls which rows are accessible. Both must match the application’s intended access model.
Are local development and self-hosting the same commitment?
No. Local development supports building and testing an application. Operating a self-hosted deployment also requires maintaining the infrastructure, configuration, updates, and service environment.

Check a Supabase Project Through MCP

Use a development project and a read-only connection to inspect its schema and verify a narrowly scoped query.