# Supabase Management API MCP Server
An MCP (Model Context Protocol) server for the Supabase Management API. This server enables AI assistants like Claude to interact with Supabase projects programmatically.
## π§ Available Tools
- **list_all_projects** - Returns a list of all your Supabase projects
- **gets_all_projects_for_the_given_organization** - Get projects for a specific organization
- **create_a_project** - Create a new Supabase project
- **lists_sql_snippets_for_the_logged_in_user** - List SQL snippets for a project
- **beta_authorize_user_through_oauth** - OAuth authorization
- **beta_exchange_auth_code_for_users_access_and_refresh_token** - Exchange OAuth code for tokens
## π¦ Getting Started
### βοΈ Prerequisites
Before starting, please ensure you have:
- [Node.js (v18+ required, v20+ recommended)](https://nodejs.org/)
- [npm](https://www.npmjs.com/) (included with Node)
Warning: if you run with a lower version of Node, `fetch` won't be present. Tools use `fetch` to make HTTP calls. To work around this, you can modify the tools to use `node-fetch` instead. Make sure that `node-fetch` is installed as a dependency and then import it as `fetch` into each tool file.
### π₯ Installation & Setup
**1. Install dependencies**
```sh
npm install
```
**2. Configure Supabase API credentials**
Create a `.env` file in the project root:
```env
SUPABASE_PUBLIC_API_API_KEY=your_personal_access_token_here
```
To get your Supabase Personal Access Token:
1. Go to [Supabase Dashboard](https://supabase.com/dashboard)
2. Click your profile β Account Settings
3. Navigate to "Access Tokens"
4. Generate a new Personal Access Token
5. Copy the token and add it to your `.env` file
**Important:** Use a Personal Access Token (JWT format), not a project API key or secret key.
## π Test the MCP Server with Postman
The MCP Server (`mcpServer.js`) exposes your automated API tools to MCP-compatible clients, such as Claude Desktop or the Postman Desktop Application. We recommend that you test the server with Postman first and then move on to using it with an LLM.
The Postman Desktop Application is the easiest way to run and test MCP servers. Testing the downloaded server first is optional but recommended.
**Step 1**: Download the latest Postman Desktop Application from [https://www.postman.com/downloads/](https://www.postman.com/downloads/).
**Step 2**: Read out the documentation article [here](https://learning.postman.com/docs/postman-ai-agent-builder/mcp-requests/create/) and see how to create an MCP request inside the Postman app.
**Step 3**: Set the type of the MCP request to `STDIO` and set the command to `node </absolute/path/to/mcpServer.js>`. If you have issues with using only `node` (e.g. an old version is used), supply an absolute path instead to a node version 18+. You can get the full path to node by running:
```sh
which node
```
To check the node version, run:
```sh
node --version
```
To get the absolute path to `mcpServer.js`, run:
```sh
realpath mcpServer.js
```
Use the node command followed by the full path to `mcpServer.js` as the command for your new Postman MCP Request. Then click the **Connect** button. You should see a list of tools that you selected before generating the server. You can test that each tool works here before connecting the MCP server to an LLM.
## π©βπ» Connect the MCP Server to Claude
You can connect your MCP server to any MCP client. Here we provide instructions for connecting it to Claude Desktop.
**Step 1**: Note the full path to node and the `mcpServer.js` from the previous step.
**Step 2**. Open Claude Desktop β **Settings** β **Developers** β **Edit Config** and add this server:
```json
{
"mcpServers": {
"supabase-management": {
"command": "node",
"args": ["/absolute/path/to/mcpServer.js"]
}
}
}
```
Replace `/absolute/path/to/` with the actual path to this project.
Restart Claude Desktop to activate this change. Make sure the new MCP is turned on and has a green circle next to it. If so, you're ready to begin a chat session that can use the tools you've connected.
**Warning**: If you don't supply an absolute path to a `node` version that is v18+, Claude (and other MCP clients) may fall back to another `node` version on the system of a previous version. In this case, the `fetch` API won't be present and tool calls will not work. If that happens, you can a) install a newer version of node and point to it in the command, or b) import `node-fetch` into each tool as `fetch`, making sure to also add the `node-fetch` dependency to your package.json.
### Additional Options
#### π³ Docker Deployment (Production)
For production deployments, you can use Docker:
**1. Build Docker image**
```sh
docker build -t <your_server_name> .
```
**2. Claude Desktop Integration**
Add Docker server configuration to Claude Desktop (Settings β Developers β Edit Config):
```json
{
"mcpServers": {
"<your_server_name>": {
"command": "docker",
"args": ["run", "-i", "--rm", "--env-file=.env", "<your_server_name>"]
}
}
}
```
> Add your environment variables (API keys, etc.) inside the `.env` file.
The project comes bundled with the following minimal Docker setup:
```dockerfile
FROM node:22.12-alpine AS builder
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm install
COPY . .
ENTRYPOINT ["node", "mcpServer.js"]
```
#### π Streamable HTTP
To run the server with Streamable HTTP support, use the `--streamable-http` flag. This launches the server with the `/mcp` endpoint enabled:
```sh
node mcpServer.js --streamable-http
```
#### π Server-Sent Events (SSE)
To run the server with Server-Sent Events (SSE) support, use the `--sse` flag. This launches the server with the `/sse` and `/messages` endpoints enabled:
```sh
node mcpServer.js --sse
```
#### π₯οΈ Stdio (Standard Input/Output)
To run the server using standard input/output (stdio), simply run the script without any flags. This mode is ideal for CLI tools or programmatic integration via stdin and stdout.
```sh
node mcpServer.js
```
## π οΈ Additional CLI commands
#### List tools
List descriptions and parameters from all generated tools with:
```sh
node index.js tools
```
Example:
```
Available Tools:
Workspace: acme-workspace
Collection: useful-api
list_all_customers
Description: Retrieve a list of useful things.
Parameters:
- magic: The required magic power
- limit: Number of results returned
[...additional parameters...]
```
## π License
MIT
## π Acknowledgments
This project was generated using the [Postman MCP Generator](https://postman.com/explore/mcp-generator).