Supabase MCP Server

What joshuarileydev/supabase-mcp-server MCP server does

The joshuarileydev/supabase-mcp-server MCP server gives MCP clients programmatic access to selected Supabase Management API operations. Its scope is administrative management of Supabase projects and organizations, not general database querying or application-level data access.

For projects, the server supports listing available projects, retrieving details for a project, creating a project, deleting a project, and obtaining project API keys. For organizations, it supports listing organizations, viewing organization details, and creating new organizations.

This makes the server relevant for workflows where an AI client needs to inspect or change Supabase account resources. It can also provide project credentials through the project API-key operation, so client access and credential-handling policies should be considered before enabling it.

How it works

The server presents Supabase Management API functions through the Model Context Protocol. An MCP-compatible client starts the server as a local process, and the process authenticates requests with the SUPABASE_API_KEY environment variable.

The README describes Claude configuration using an MCP server entry named supabase. The client launches the package with npx, while the API key is provided in the entry's environment configuration. Once connected, the AI client can invoke the supported project and organization management operations through the MCP interface.

The joshuarileydev/supabase-mcp-server MCP server therefore depends on both a compatible MCP client and a Supabase API key. The supplied material does not document required Supabase account roles, API endpoint overrides, transport alternatives, or detailed request parameters.

Setup and configuration

Install or run the package from an MCP client's server configuration. The documented setup uses the npm package @joshuarileydev/supabase-mcp-server and the npx runner. Configure the server process with:

• SUPABASE_API_KEY: the Supabase API key used to access the Management API.

The README shows Claude Desktop as the configuration target. The example uses a JSON object under mcpServers, with command set to npx, the package passed as an argument, and the API key supplied under env.

Use a valid key in place of the example value and protect the configuration because the server can perform mutating operations, including project deletion and organization creation. No additional environment variables or configuration files are described in the provided material.

Tools and capabilities

Supported capability groups are:

• List, inspect, create, and delete Supabase projects.
• Retrieve API keys for Supabase projects.
• List and inspect Supabase organizations.
• Create Supabase organizations.

The joshuarileydev/supabase-mcp-server MCP server is focused on these Management API actions. The material does not identify individual MCP tool names, filtering options, pagination behavior, project-region controls, or organization-membership operations.

Limitations and notes

The documented feature set covers Supabase projects and organizations only. It does not state that the server can run SQL, read or write tables, manage authentication users, configure storage, or deploy application code. Those capabilities should not be assumed from the Supabase branding alone.

The README requires an API key but does not specify its permission scope, rotation process, or whether different keys are supported. It also does not provide a license, hosted endpoint, pricing information, troubleshooting guidance, or compatibility details for clients other than Claude Desktop.

Because the server can create and delete resources, use an API key with permissions appropriate to the intended automation and review destructive actions before allowing an agent to invoke them.