01 / CAPABILITY
LI
Live PostgreSQL schema
Let the AI client inspect Supabase tables, columns, foreign keys, indexes, and generated descriptions before writing SQL.
Supabase / PostgreSQL / hosted MCP
Supabase MCP server: platform or database access?
Choose the smallest useful tool surface.
Compare the official Supabase MCP server with a database-focused DataMCP connection. Use Supabase platform tools when you need them, or publish scoped PostgreSQL schema and query tools through a hosted MCP link.
Official-vs-database comparison1 database + 1 link freeRead-only and custom policies
LIVE ROUTEACCESS POLICY / ENFORCED
SOURCESupabase PostgreSQLschema discovered
GATEWAYdatamcpauth · policy · route
CLIENTAI clientshosted MCP link
REQUEST
tools/call → productionPOLICY CHECKEDAUTHOAuth 2.0
ACCESSScoped
SECRETSEncrypted
ROUTEHosted
The production path
Choose the MCP surface that matches the job
Supabase has an official hosted MCP server for Supabase-specific development and project workflows. DataMCP is not that server. It connects to the PostgreSQL database behind a Supabase project using standard database credentials and exposes PostgreSQL schema and query tools through a hosted remote MCP endpoint.
Choose the official server when the AI client needs platform tools such as migrations, logs, advisors, Edge Functions, generated types, or project administration. Scope it to one project and restrict feature groups: without a selected project, the official server can access every project available to the authorized Supabase organization. Choose a DataMCP PostgreSQL connection when the task is database-focused and each client or environment needs a separate SQL permission boundary and revocation path.
For the complete Cursor configuration, connection-mode guidance, and restricted-role SQL, follow the Supabase to Cursor MCP tutorial.
What you get
Production access.
Without production guesswork.
02 / CAPABILITY
SC
Scoped SQL operations
Create read-only, read-write, full-access, or custom table-level MCP links while retaining the PostgreSQL role as another boundary.
03 / CAPABILITY
EN
Encrypted database credential
Keep the Supabase PostgreSQL connection string encrypted at rest instead of copying it into Cursor, Claude, or VS Code configuration.
04 / CAPABILITY
SE
Separate MCP links
Give different clients, people, or environments distinct authentication and permission scopes without sharing the database password.
05 / CAPABILITY
PO
PostgreSQL query history
Review database queries and denied operations by connection and MCP link in the DataMCP activity view.
06 / CAPABILITY
PR
Provider-independent workflow
Use the same hosted PostgreSQL MCP model for Supabase, Neon, RDS, and other compatible PostgreSQL providers.
Source to controlled MCP link
One. Two.
Three.
Connect the source once. DataMCP handles discovery, hosted transport, client authentication, and link policy.
Read the setup guide- 01Copy PostgreSQL credentials
Get the direct or session-pooler connection string from the Supabase Connect panel, preferably for a restricted database role.
- 02Create a scoped MCP link
Add the PostgreSQL connection to DataMCP and start with a read-only or table-specific permission policy.
- 03Connect the AI client
Copy the generated remote MCP configuration into Cursor, Claude, ChatGPT, or VS Code and verify schema access before querying rows.
Build or use datamcp
Official Supabase MCP vs. DataMCP
See what stays on your engineering backlog when the MCP runtime and control layer are managed for you.
CAPABILITYDATAMCPOfficial Supabase MCP
Primary scopePostgreSQL schema and queries
Supabase platform and project workflows
Authentication pathDataMCP client auth + PostgreSQL role
Supabase authorization to the selected organization
NarrowingMCP link and table operations
Project, read-only mode, and feature groups
Platform toolsNot exposed
Migrations, logs, advisors, Edge Functions, and more
DataMCP query activityPostgreSQL queries and denials
Not routed through DataMCP
Frequently asked questions
Questions before
you connect.
Clear answers about architecture, access, credentials, and supported clients.
Is DataMCP the official Supabase MCP server?
No. Supabase provides its own official MCP server for Supabase platform and project workflows. DataMCP connects to the underlying Supabase PostgreSQL database with standard PostgreSQL credentials and exposes database schema and query tools.
When should I use the official Supabase MCP server?
Use the official server when an AI client needs Supabase-specific tools such as project management, migrations, logs, advisors, Edge Functions, or generated types. Use DataMCP when the job is controlled PostgreSQL schema and SQL access with separate MCP links, table-level operation policies, and query activity review.
Can I make Supabase MCP access read-only?
Yes. A DataMCP read-only link allows PostgreSQL schema inspection and SELECT queries while blocking writes. The connected PostgreSQL role remains an independent permission boundary, so a dedicated read-only database role is recommended for sensitive environments.
Does DataMCP expose Supabase Auth, Storage, or Edge Functions?
No. DataMCP's Supabase workflow is a standard PostgreSQL connection. It does not expose Supabase Auth, Storage, Edge Functions, project logs, migrations, advisors, organization management, or other Supabase platform tools.
Does the AI client receive my Supabase database password?
No. DataMCP stores the PostgreSQL connection string encrypted at rest with AES-256-GCM. The AI client receives a hosted MCP endpoint and DataMCP authentication credential, not the database password.
Should I connect the official Supabase MCP server to production?
Supabase explicitly recommends using its MCP server with development or test projects rather than production data. If real data must be accessed, Supabase recommends read-only mode, project scoping, restricted feature groups, and manual tool approval. A DataMCP database connection should likewise use a dedicated least-privilege PostgreSQL role and a narrow MCP link.
Does the official Supabase MCP server require a personal access token?
Not for the normal hosted setup. Supabase now uses a browser-based authorization flow for compatible MCP clients. Personal access tokens remain an option for CI or clients that cannot complete the interactive flow.
Keep exploring
Related guides.
GUIDE
Connect Supabase to Cursor
Compare both MCP routes, choose the right Supabase connection mode, and configure restricted database access step by step.
GUIDEHosted PostgreSQL MCP server
Review the complete PostgreSQL tool, permission, authentication, and activity model.
GUIDECursor PostgreSQL MCP
Add a project-scoped hosted MCP endpoint to Cursor without storing the database password in mcp.json.
GUIDEClaude PostgreSQL MCP
Connect Claude to a controlled PostgreSQL endpoint and keep database credentials server-side.
GUIDECompare PostgreSQL MCP servers
Compare official provider servers, local open-source tools, and hosted PostgreSQL access gateways.
Start with one link
Give AI controlled access to Supabase PostgreSQL
Connect one Supabase PostgreSQL database and create one hosted MCP link on the Free plan.