Supabase MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Supabase MCP Server?

Supabase MCP Server is a tool that enables Cursor and Windsurf IDEs to interact directly with Supabase PostgreSQL databases, providing a seamless database management experience.

How to use Supabase MCP Server?

To use the Supabase MCP Server, clone the repository, set up your environment, and configure your IDE to connect to the server. You can run it locally or in a production environment.

Key features of Supabase MCP Server?

  • 💻 Compatibility with both Windsurf and Cursor IDEs
  • ✅ Support for local and production Supabase projects
  • 🔨 Built-in database exploration tools with schema insights
  • 🔐 Secure read-only database access
  • 🔍 SQL query validation

Use cases of Supabase MCP Server?

  1. Managing local Supabase databases during development.
  2. Connecting IDEs to production databases for real-time data management.
  3. Validating SQL queries before execution.

FAQ from Supabase MCP Server?

  • Can I use Supabase MCP Server with other IDEs?

Currently, it is designed to work specifically with Cursor and Windsurf IDEs.

  • Is there a cost associated with using Supabase MCP Server?

No, it is open-source and free to use.

  • What are the prerequisites for using Supabase MCP Server?

You need Python 3.12+, PostgreSQL 16+, and the uv package manager.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago