MCP & CONNECTED TOOLS
Supabase MCP for Claude Code Setup and Verification
Scope the Supabase project before connecting Claude Code or Cursor. The server URL controls project and tool access; the client controls where configuration lives and how sign-in starts.
On this page
SupabaseProject scope → client sign-in → read check
01No selected project means all accessible projects are in scope.
02Claude Code and Cursor use different project configuration files.
03A connected status still needs a check of the intended project.
Start with one practical task
Choose the Supabase project first, then verify the Claude Code connection with a small read. Check the returned project context and access scope before asking the agent to act on data.
Generate a scoped server URL
Supabase’s panel exposes project_ref, read_only and features. Selecting a project narrows access; leaving it unselected exposes all accessible projects. Start a diagnostic connection with only the groups the task needs.
Use the client’s own configuration
Claude Code supports project .mcp.json and HTTP setup; Supabase instructs regular-terminal /mcp authentication. Cursor uses project .cursor/mcp.json or personal ~/.cursor/mcp.json. Do not paste one client’s file into another unchanged.
Verify connection, then verify scope
Check the client’s server status and discovered tools, then request a harmless description of the intended project or schema. If a tool is absent, inspect feature groups, read-only mode and permissions before changing credentials.
A few more details
Do all interactive clients need a personal access token?
No. Hosted Supabase MCP normally uses browser OAuth/dynamic registration; special CI or client cases have separate manual paths.
Is a connected badge enough?
No. Confirm the intended project, permissions and harmless read result as well.
Sources & maker notes
This guide is based on the cited documentation and maker sources. vibeforthat has not run an independent installation or end-to-end product test for this article.
Related guides & projects
View all
Supabase MCP Read-Only Mode and Project Scope
Use project_ref and read_only to narrow a Supabase MCP connection. See what each setting controls and how to confirm the right project.
Read more
Lovable and Supabase Setup for Auth and Data
You do not need a separate Supabase account for every Lovable app. Connect your own project when you need its dashboard, billing or existing data—and plan the move, because the two backend routes do not migrate automatically.
Read moreMCP vs Skills for Agent Workflows
A skill teaches a procedure; MCP connects the agent to a system. A database review can need both: instructions for the review and an authorized way to read the schema.
Read moreSupabase Row Level Security
Write down who can read and change each row before writing a policy. Then check the owner, another user and a signed-out request through the same client path the app will use.
Read more