npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

polardb-supabase-mcp

v1.0.7

Published

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

Readme

PolarDB Supabase MCP Server

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_edge_function_secrets: Lists all Edge Function secrets (encrypted values)
  • create_edge_function_secrets: Creates or updates Edge Function secrets (supports batch operations, values are encrypted)
  • delete_edge_function_secrets: Deletes Edge Function secrets (supports batch deletion)

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.