Supabase MCP Server

Created By
MCP-Mirrora year ago
Mirror of
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 other clients to manage Supabase projects and organizations through a standardized interface.

how to use Supabase MCP Server?

To use the Supabase MCP Server, add the provided configuration to your Claude Config JSON file, specifying the command and API key for Supabase.

key features of Supabase MCP Server?

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

use cases of Supabase MCP Server?

  1. Automating project management tasks in Supabase.
  2. Integrating Supabase management into AI applications.
  3. Streamlining organization management for multiple Supabase projects.

FAQ from Supabase MCP Server?

  • What is the purpose of the Supabase MCP Server?

It provides a standardized way to manage Supabase projects and organizations programmatically.

  • How do I install the Supabase MCP Server?

You can install it by adding the specified configuration to your Claude Config JSON file.

  • Can I manage multiple Supabase projects with this server?

Yes, the server allows you to manage multiple projects and organizations efficiently.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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