supabase-mcp-setup

Configure the Supabase MCP server with a local .mcp.json file and project-specific environment variables.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/WebSmartTeam/COR-CODE --skill supabase-mcp-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-mcp-setup
Source: https://github.com/WebSmartTeam/COR-CODE/tree/main/skills/supabase-mcp-setup
Command: npx skills add https://github.com/WebSmartTeam/COR-CODE --skill supabase-mcp-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of configuring the Supabase MCP (Multi-Channel Platform) server for individual projects, ensuring that database queries are directed to the correct project-specific database and preventing accidental cross-database operations.

Core Features & Use Cases

  • Project-Specific Configuration: Sets up MCP to use a local .mcp.json file tailored to a specific project's Supabase instance, rather than a global configuration.
  • Secure Authentication: Integrates Supabase's SUPABASE_ACCESS_TOKEN for secure API access.
  • Use Case: When starting a new project that utilizes Supabase, this Skill guides you through creating the necessary local configuration file and environment variable setup to connect Claude Code to your project's Supabase database for data operations.

Quick Start

Follow the steps in this guide to create a .mcp.json file in your project root and add your Supabase access token to your .env.local file.

Frequently Asked Questions about supabase-mcp-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Supabase MCP for a specific project?

Configure Supabase MCP for a specific project by creating a local .mcp.json file in your project root and adding your Supabase Project Reference ID and SUPABASE_ACCESS_TOKEN to the environment variables for scoped API interactions.

Why do I need a local .mcp.json file for Supabase database access?

A local .mcp.json file isolates database access to a specific Supabase instance, preventing accidental cross-database operations in multi-project environments compared to using a global configuration.

What credentials do I need to set up Supabase MCP server connections?

You need your Supabase Project Reference ID and a SUPABASE_ACCESS_TOKEN to set up the MCP server, ensuring secure and scoped API interactions with your project's database.

Can I use Supabase MCP to isolate database access across multiple projects?

Yes, you can isolate database access across multiple projects by setting up a local .mcp.json file tailored to each individual Supabase instance rather than relying on a global configuration.

Does Supabase MCP configuration require global environment variables?

No, Supabase MCP configuration uses local environment variables by adding the SUPABASE_ACCESS_TOKEN to your .env.local file, ensuring database queries are securely directed to the correct project-specific database.