Supabase MCP Server
Supabase MCP Server
Connect Claude to Supabase through Supabase's official remote MCP Server.
The Supabase MCP Server enables Claude to query tables, inspect schemas, manage project settings, and interact with your Supabase database using natural language.
What Can Claude Do with the Supabase MCP Server?
The Supabase MCP Server exposes Supabase functionality to Claude through the Model Context Protocol.
Core capabilities:
- Query Data — Retrieve records from tables using natural language descriptions
- Inspect Schemas — View table structures, column types, and relationships
- Manage Project Settings — Access parts of your Supabase project configuration
- View Logs and Analytics — Monitor database activity and performance
- Manage Authentication — Access user and auth-related information
Actual capabilities depend on the current Supabase MCP toolset and your granted permissions.
Access scope: Claude can only access data and features your authorization allows. The integration respects Supabase Row Level Security policies and project permissions.
How to Install the Supabase MCP Server
Supabase provides an official remote MCP Server.
For Claude Code
Use Claude Code's MCP management to add the remote Supabase MCP endpoint:
Connection endpoint: https://mcp.supabase.com/mcp
Authentication uses browser-based OAuth authorization in the default flow. You'll be redirected to authorize access during setup.
For Claude Desktop
Use the remote MCP endpoint supported by your MCP client. Check Claude Desktop's current documentation for remote MCP configuration instructions.
Supabase MCP Authentication
The Supabase MCP Server uses browser-based authentication in the default flow.
Authorization process:
- When you connect to the Supabase MCP endpoint, you'll be redirected to a browser
- You authorize access at the organization or project level
- Access credentials are managed automatically
- Claude can access authorized Supabase projects
Important: Personal Access Tokens (PAT) are no longer required for the standard interactive setup. Authorization happens through the browser during initial connection.
Access is granted at:
- Organization level (access to multiple projects)
- Project level (access to specific projects)
You control which projects Claude can access during the authorization flow.
Supabase MCP Use Cases & Query Examples
Example workflows that become possible with the Supabase MCP Server.
Query Table Data
Example prompt:
> "Show me all users from the profiles table where status is 'active'."
Claude can query your Supabase tables based on the conditions you describe.
Inspect Database Schema
Example prompt:
> "What columns are in the orders table and what are their types?"
Claude can retrieve and display table schema information.
Filter and Aggregate Data
Example prompt:
> "Count how many posts were created in the last 7 days, grouped by category."
Claude can perform filtering and aggregation queries on your data.
Check Auth Status
Example prompt:
> "List all users who signed up today."
Claude can query authentication data within your permission scope.
View Project Configuration
Example prompt:
> "Show me the current database connection settings for my project."
Claude can access project configuration information exposed through the MCP server.
Note: These are example use cases. Actual capabilities depend on your Supabase project configuration and the permissions you've granted during authorization.
Supabase MCP in a Postgres App Stack
Supabase MCP is usually used where teams want Claude to work against Postgres-backed apps, auth flows, and project operations.
What this shows: This screenshot shows the Supabase MCP repository, which reflects the practical tool surface teams use for project access, SQL tasks, and assistant-driven database operations.
Why this scenario matters: It shows the real project layer where Supabase MCP is useful, especially when assistants need to reason about database-backed apps, auth, and project resources together.
Typical assistant task: Work with project resources, SQL-centric data flows, and auth-aware app operations in one MCP surface.
Source: Supabase MCP Repository
When to Pick Supabase MCP Server vs Firebase Firestore
This comparison is most useful when both options look plausible on paper but differ in operating model, team fit, and day-to-day workflow cost.
| Decision Lens | This Page's MCP Path | Competitor |
|---|---|---|
| Best For | Teams building Postgres-backed apps and wanting assistant access to SQL-centric project operations. | Teams favoring document-first realtime data patterns and Firebase-style app workflows. |
| Where MCP Wins | Supabase MCP wins when the assistant should operate close to SQL, relational models, and policy-aware database work. | |
| Tradeoff to Watch | It is a weaker fit than Firestore when the real application model is document-first and sync-heavy rather than relational. | |
| Choose This Path When | Choose Supabase MCP for Postgres and SQL-led app stacks; choose Firestore when realtime document workflows are the better fit. | |
| Sources | ||
Frequently Asked Questions
Is the Supabase MCP Server free?
Do I need to create a Personal Access Token?
Can Claude write to my database?
Does it work with Supabase local development?
What if Claude reports connection errors?
What's the difference between organization and project access?
Where can I find my Supabase project details?
Use Supabase MCP in Verdent
Verdent provides streamlined Supabase integration. This is Verdent's platform-level integration flow, not the default setup path from Supabase's official documentation.
Connect your Supabase project once and access database operations across all Verdent projects without repeated authorization flows.