Query | MCP server for Supabase

Created By
alexander-zueva year ago
Query MCP enables end-to-end management of Supabase via chat interface: read & write query executions, management API support, automatic migration versioning, access to logs and much more.
Overview

What is Supabase MCP Server?

Supabase MCP Server is a Model Context Protocol (MCP) server that provides programmatic access to the Supabase Management API, allowing AI models and clients to manage Supabase projects and organizations through a standardized interface.

How to use Supabase MCP Server?

To use Supabase MCP Server, integrate it by adding the required configuration to your Claude Config JSON file, specifying your Supabase API key and the command for npx to run the server.

Key features of Supabase MCP Server?

  • Project Management: List, create, delete projects, and retrieve project API keys.
  • Organization Management: List and create organizations, and fetch organization details.

Use cases of Supabase MCP Server?

  1. Automating the management of Supabase projects programmatically.
  2. Integrating AI systems with Supabase for effortless project and organization handling.
  3. Simplifying API interactions for developers using Supabase services.

FAQ from Supabase MCP Server?

  • What is the main function of Supabase MCP Server?

It provides a standardized interface for managing Supabase projects and organizations through programmatic access.

  • Is Supabase MCP Server free to use?

Yes! The server can be used freely along with the Supabase platform, subject to Supabase's pricing plans for usage.

  • What prerequisites are needed to use Supabase MCP Server?

You need to have a Supabase account and an API key to configure and run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
alexander-zuev
Star
714
Language
Python
License
Apache-2.0 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