- Home
- MCP servers
- Supabase
Supabase
- javascript
0
GitHub Stars
javascript
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"zain4391-supabase_mcp": {
"command": "node",
"args": [
"mcpServer.js"
],
"env": {
"SUPABASE_PUBLIC_API_API_KEY": "YOUR_PERSONAL_ACCESS_TOKEN"
}
}
}
}This MCP server enables AI assistants to interact with Supabase projects programmatically. You can list projects, create new ones, manage SQL snippets, and handle OAuth flows through a local MCP-compatible runner, making it easier to automate administration and workflows.
How to use
You connect an MCP client to the server and expose its available tools to the assistant. The server provides a set of actions you can invoke to manage Supabase projects, retrieve information, and handle OAuth-based authentication flows. Use the client’s MCP configuration to enable and run the server locally, then test each tool to verify it operates as expected.
Once connected, you can perform these actions through the MCP client/workflow: list all projects, get projects for a specific organization, create a new project, list SQL snippets for a project, authorize users via OAuth, and exchange authorization codes for user access and refresh tokens.
How to install
Prerequisites: ensure you have Node.js installed (v18 or newer is required; v20+ is recommended). You should also have npm installed along with your Node.js distribution.
Step 1. Install dependencies
npm install
Step 2. Configure Supabase API credentials by creating a .env file in the project root with your personal access token
SUPABASE_PUBLIC_API_API_KEY=your_personal_access_token_here
How to obtain your token: open the Supabase Dashboard, go to your profile → Account Settings → Access Tokens, generate a new Personal Access Token, and copy it into the .env file. Use a Personal Access Token (JWT format) rather than a project API key or secret key.
Step 3. Run the server in stdio mode
node mcpServer.js
Additional options
If you want to expose the server over HTTP or enable streaming features, you can run with specific flags or via Docker. The following options are commonly used in production or testing scenarios.
Security and environment
Keep your .env file secure and do not commit it to version control. Only expose the necessary tokens and credentials to the running environment. When deploying, provide environment variables securely through your hosting platform.
Available tools
list_all_projects
Return 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 flow to authorize users.
beta_exchange_auth_code_for_users_access_and_refresh_token
Exchange an OAuth authorization code for user access and refresh tokens.