Servidor MCP do Supabase

What is Servidor MCP do Supabase?

Servidor MCP do Supabase is an MCP server that provides a RESTful API for interacting with Supabase. It allows querying, inserting, and updating data in Supabase tables. It is intended for developers who need a simple HTTP-based interface to their Supabase projects.

How to use Servidor MCP do Supabase?

Install dependencies with npm install, copy .env.example to .env, and fill in your SUPABASE_URL and SUPABASE_KEY. Start the server with npm start. For production, deploy to Smithery using the Smithery CLI (smithery login, smithery deploy) and set the same environment variables in the Smithery dashboard.

Key features of Servidor MCP do Supabase

• Query all records from a table via GET /api/:table
• Retrieve a specific record by ID via GET /api/:table/:id
• Insert new records via POST /api/:table
• Update existing records via PATCH /api/:table/:id
• Deploy and monitor on Smithery platform

Use cases of Servidor MCP do Supabase

• Expose Supabase data to any HTTP client (e.g., curl, web apps)
• Build quick CRUD backends without writing custom server logic
• Prototype or integrate with MCP‑compatible tools and agents

FAQ from Servidor MCP do Supabase

What does the server do?

It provides a RESTful API to query, insert, and update data in Supabase tables through standard HTTP methods.

What are the prerequisites for running the server?

You need Node.js, npm, an active Supabase project, and your project’s URL and API key.

How do I deploy the server to Smithery?

Install the Smithery CLI (npm install -g @smithery/cli), log in (smithery login), run smithery deploy, and set SUPABASE_URL and SUPABASE_KEY as environment variables in the Smithery dashboard.

What endpoints are available?

GET /api/:table (list), GET /api/:table/:id (read single), POST /api/:table (create), and PATCH /api/:table/:id (update).

Where is the data stored?

Data lives in your Supabase project, configured via the SUPABASE_URL and SUPABASE_KEY environment variables.