Supabase MCP Server

Supabase MCP Server is a MCP server built around supabase's official MCP server, connecting agents to project configuration, databases, and developer tools through hosted OAuth or a local endpoint. Its value is practical: read project and database information and assist database development are available from one documented project, while the repository remains inspectable before it is added to an agent workflow.

Set up Supabase MCP Server from its public GitHub instructions, keep the initial permission scope small, and verify it with a low-risk task before regular use.

Help me set up Supabase MCP Server.
Project URL: https://github.com/supabase/mcp

Read the repository README and license first. Confirm the current host, prerequisites, destination paths, and permissions. Follow the repository's documented method, keep credentials out of files and logs, and start with the least-privilege or read-only option where available. Afterward, run a small verification and report the exact changes, commands, configuration path, and result. Ask before overwriting files or requesting broader access.

{"mcpServers":{"supabase":{"type":"http","url":"https://mcp.supabase.com/mcp"}}}

1. 1
   Review prerequisites and scope

   Read the README, confirm the target host, and prepare these prerequisites: A Supabase account with target project access; An MCP host that supports HTTP transport and OAuth. Check destination paths and permissions before making changes.

2. 2
   Apply the documented setup

   Add the following configuration to the current MCP host: {"mcpServers":{"supabase":{"type":"http","url":"https://mcp.supabase.com/mcp"}}}

3. 3
   Verify with a small task

   Restart the MCP host and confirm that Supabase MCP Server appears in the server list. Call one low-risk read-only tool and check that it returns an expected result without authentication errors.

This assessment is based on the repository README, component documentation, license, and maintenance metadata. The hosted endpoint uses OAuth instead of a manually copied long-lived token; Both hosted projects and local development are supported. The main trade-offs are also clear: The agent may receive database and project-management capabilities; Local and self-hosted endpoints differ from the hosted service. No local installation or functional test was claimed during cataloging.