Command Palette

Search for a command to run...

UnylyUnyly
Browse all

PolarDB Supabase

FreeNot checked

PolarDB Supabase — Model Context Protocol server

GitHubEmbed

About

PolarDB Supabase — Model Context Protocol server

README

Connect your PolarDB Supabase instances to Cursor, Claude, Windsurf, and other AI assistants.

The Model Context Protocol (MCP) standardizes how Large Language Models (LLMs) talk to external services like Supabase. This server connects AI assistants directly with your PolarDB Supabase project and allows them to perform tasks like managing tables, fetching config, and querying data.

Prerequisites

You will need Node.js installed on your machine. You can check this by running:

node -v

If you don't have Node.js installed, you can download it from nodejs.org.

Setup

1. Get your PolarDB credentials

You'll need the following from your PolarDB instance:

  • API URL: Your PolarDB instance endpoint (e.g., http://your-host:port)
  • Service Role Key: For database operations and as fallback authentication for Edge Functions/secrets
  • Dashboard Username/Password (Optional): For Edge Functions, secrets management, and type generation (if not provided, Service Role Key will be used)

2. Configure your MCP client

Configure your MCP client (such as Cursor) to use this server. Most MCP clients store the configuration as JSON.

Option 1: Using npx (Recommended - No local build required)

{
  "mcpServers": {
    "polardb-supabase": {
      "command": "npx",
      "args": [
        "-y",
        "polardb-supabase-mcp",
        "--api-url",
        "http://your-polardb-supabase-host:port",
        "--service-role-key",
        "your-service-role-key",
        "--anon-key",
        "your-anon-key",
        "--dashboard-username",
        "your-dashboard-username",
        "--dashboard-password",
        "your-dashboard-password",
        "--project-ref",
        "default"
      ]
    }
  }
}

Option 2: Using local build

{
  "mcpServers": {
    "polardb-supabase": {
      "command": "node",
      "args": [
        "/path/to/supabase-mcp/packages/mcp-server-supabase/dist/transports/stdio.js",
        "--api-url",
        "http://your-polardb-supabase-host:port",
        "--service-role-key",
        "your-service-role-key",
        "--anon-key",
        "your-anon-key",
        "--dashboard-username",
        "your-dashboard-username",
        "--dashboard-password",
        "your-dashboard-password",
        "--project-ref",
        "default"
      ]
    }
  }
}

Replace the placeholder values with your actual PolarDB credentials.

Security

Before running the MCP server, we recommend you read our security best practices to understand the risks of connecting an LLM to your PolarDB projects and how to mitigate them.

Read-only mode

To restrict the server to read-only queries, set the --read-only flag:

node /path/to/supabase-mcp/packages/mcp-server-supabase/dist/transports/stdio.js --read-only

We recommend you enable this by default. This prevents write operations on your databases, including creating or deleting Edge Function secrets.

Tools

The following tools are available to the LLM:

Database

  • list_tables: Lists all tables within the specified schemas
  • execute_sql: Executes raw SQL in the database

Development

  • get_project_url: Gets the API URL for a project
  • get_anon_key: Gets the anonymous API key for a project

Edge Functions

  • list_edge_functions: Lists all Edge Functions in a project
  • get_edge_function: Gets details for a specific Edge Function
  • deploy_edge_function: Deploys a new Edge Function to a project

Edge Functions Secrets

  • list_ef_secrets: Lists all Edge Function secrets (encrypted values).
  • create_ef_secrets: Creates or updates Edge Function secrets (batch supported; values are encrypted).
  • delete_ef_secrets: Deletes Edge Function secrets (batch deletion supported).

Note: Secrets management supports two authentication methods: Dashboard authentication (username/password) is preferred, but Service Role Key can also be used. Secrets are automatically encrypted when stored.

AI Prompts

  • get_best_practices: List all available Supabase AI prompts and development guidance

Resources

License

This project is licensed under Apache 2.0. See the LICENSE file for details.

from github.com/ApsaraDB/PolarDB-Supabase-MCP-Server

Installing PolarDB Supabase

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/ApsaraDB/PolarDB-Supabase-MCP-Server

FAQ

Is PolarDB Supabase MCP free?

Yes, PolarDB Supabase MCP is free — one-click install via Unyly at no cost.

Does PolarDB Supabase need an API key?

No, PolarDB Supabase runs without API keys or environment variables.

Is PolarDB Supabase hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install PolarDB Supabase in Claude Desktop, Claude Code or Cursor?

Open PolarDB Supabase on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare PolarDB Supabase with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All development MCPs