Supabase Mcp Server

Created By
medieagea year ago
Overview

What is Supabase MCP Server?

Supabase MCP Server is a tool that enables developers to manage their Supabase databases, execute SQL queries, and handle user authentication with built-in safety controls.

How to use Supabase MCP Server?

To use the Supabase MCP Server, install it via a package manager like pipx or uv, configure it with your Supabase project details, and connect it to your preferred MCP client such as Cursor or Windsurf.

Key features of Supabase MCP Server?

  • Compatibility with various MCP clients supporting stdio protocol.
  • Control over read-only and read-write modes for SQL query execution.
  • Runtime SQL query validation with risk level assessment.
  • Robust transaction handling and automatic versioning of database schema changes.
  • Management of Supabase projects and users through the Supabase Management API.

Use cases of Supabase MCP Server?

  1. Executing complex SQL queries safely in a development environment.
  2. Managing user authentication and roles in Supabase projects.
  3. Automating database schema migrations and versioning.

FAQ from Supabase MCP Server?

  • Is Supabase MCP Server free to use?

Yes! The core tool is free and open-source.

  • What programming language is required?

You need Python 3.12 or higher to run the server.

  • Can I use it for local development?

Yes, it supports local development setups as well as remote Supabase projects.

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

Recommend Servers

View All
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)

2 days ago