Supabase MCP Server

Created By
haladesignsa year ago
A Model Context Protocol (MCP) server that provides AI assistants with the ability to interact with Supabase databases through standardized tools.
Overview

What is Supabase MCP Server?

Supabase MCP Server is a Model Context Protocol (MCP) server that enables AI assistants to interact with Supabase databases using standardized tools.

How to use Supabase MCP Server?

To use the Supabase MCP Server, clone the repository, set up a virtual environment, install dependencies, configure environment variables, and run the server.

Key features of Supabase MCP Server?

  • Read rows from tables with filtering and column selection
  • Create single or multiple records
  • Update records with flexible filtering
  • Delete records safely with filter conditions
  • Environment-based configuration
  • Stdio transport support

Use cases of Supabase MCP Server?

  1. Integrating AI assistants with Supabase databases for data retrieval.
  2. Automating data entry and updates in Supabase tables.
  3. Building applications that require dynamic interaction with database records.

FAQ from Supabase MCP Server?

  • What programming language is Supabase MCP Server written in?

Supabase MCP Server is written in Python.

  • Is there a license for using Supabase MCP Server?

Yes, it is licensed under the MIT License.

  • How can I contribute to the project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
haladesigns
Star
0
Language
Python
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)

a day ago