What are the runtime dependencies?
Python 3.12 or later is required. PostgreSQL libraries are no longer needed because the server uses `asyncpg`. For local Supabase instances, PostgreSQL 16+ must be installed separately.
@medieage
Basic information
No overview available yet
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"supabase-mcp-server-medieage": {
"command": "uv",
"args": [
"pip",
"install",
"supabase-mcp-server"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Supabase MCP Server is an MCP server that enables your favorite IDE to safely execute SQL queries, manage your database end-to-end, access the Supabase Management API, and handle user authenticationโall with built-in safety controls. It is designed for developers using Cursor, Windsurf, Cline, or any MCP client that supports the stdio protocol.
Install the server via pipx install supabase-mcp-server or uv pip install supabase-mcp-server, then configure it with environment variables or a global .env file. The server requires a Supabase project reference, database password, and optionally an access token and service role key for Management API and Auth Admin features.
Python 3.12 or later is required. PostgreSQL libraries are no longer needed because the server uses `asyncpg`. For local Supabase instances, PostgreSQL 16+ must be installed separately.
It connects to your Supabase PostgreSQL database using the transaction pooler endpoint. For remote projects, the connection string is built from the project reference, password, and region. Session pooling is not supported; only transaction pooling is used.
Configuration is read from environment variables, a local `.env` file (when running from source), or a global config file at `~/.config/supabase-mcp/.env` on macOS/Linux or `%APPDATA%\supabase-mcp\.env` on Windows.
The server does not support self-hosted Supabase instances, custom connection strings, or session pooling. Management API and Auth Admin features only work with remote Supabase projects, not local development.
The server uses environment variables for authentication. `SUPABASE_DB_PASSWORD` is required for database access. `SUPABASE_ACCESS_TOKEN` enables the Management API, and `SUPABASE_SERVICE_ROLE_KEY` enables the Auth Admin SDK. All connections are made over `stdio` transport.
Put the project you are working on online. Deploys the current folder or a GitHub repo to a live HTTPS URL on Dockhold; reads status and logs, sets variables, resizes apps and databases...

Nippy is drag-and-drop hosting (nippy.host) with an MCP server: connect it and your assistant can publish HTML, folders of photos, or file downloads to a live *.nippy.site URL โ and keep editing the site in place at the

Web hosting for websites built with AI. Connect your HostingFor.AI account and your AI assistant can publish and maintain your site directly: upload files, manage DNS records for custom domains, run SQL against your MySQ
The official Webshare MCP server. Manage your proxies, usage, plans and billing from Claude, Cursor or any MCP client. Sign in with OAuth, no API key.
Official OutageDeck MCP server for vendor-published cloud and SaaS status, incident timelines, and observed uptime history.
Comments