Supabase MCP Server 🚀

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Supabase MCP Server?

Supabase MCP Server is a powerful Model Context Protocol (MCP) server that provides full administrative control over your Supabase PostgreSQL database through Cursor's Composer and Codeium's Cascade.

How to use Supabase MCP Server?

To use the Supabase MCP Server, clone the repository, install dependencies, build the project, and configure it with your Supabase project details. You can then manage your database using natural language commands in Cursor's Composer.

Key features of Supabase MCP Server?

  • Full suite of database management tools including table operations, record management, and schema modifications.
  • Integration with Cursor's Composer for natural language database management.
  • Support for Codeium's Cascade for advanced users.

Use cases of Supabase MCP Server?

  1. Managing PostgreSQL databases through conversational commands.
  2. Automating database operations like creating tables and managing records.
  3. Integrating with development environments for seamless database management.

FAQ from Supabase MCP Server?

  • What is the purpose of the Supabase MCP Server?

It provides a user-friendly interface for managing PostgreSQL databases using natural language commands.

  • Is it free to use?

Yes, the Supabase MCP Server is open-source and free to use.

  • What are the prerequisites?

You need Node.js, npm, and a Supabase project with the necessary credentials.

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago