Supabase Remote MCP server

What's changed?#

The Supabase MCP server is now hosted as a remote (HTTP) MCP server at the following URL:

Or if you are developing locally using the CLI, you can access the MCP server at:

This makes it easier and more secure to connect your MCP clients with Supabase while expanding the number of clients Supabase can connect to.

Why remote MCP?#

Up until now you had to run Supabase MCP locally via an npx command:

Running the MCP server this way came with a lot of pain points:

1. Limited MCP clients: Most web-based AI agents (like ChatGPT) are limited to HTTP-based MCP servers due to the environments they run in.
2. Authentication was clunky: You needed to manually generate a personal access token (PAT) in order to authenticate with your Supabase account which added friction to the setup experience and had weaker security (it was easy to accidentally commit this to source control).
3. Setup was tricky: You needed Node.js installed to run the server, needed to make sure your environment was configured correctly with the right version, and you needed to modify the command slightly based on the operating system you were running.

Now with remote MCP, you are able to connect Supabase with many more MCP clients, you authenticate using a much simpler browser-based OAuth 2 flow, and setup is much easier. We also built an interactive widget to help you connect popular MCP clients to Supabase and customize the URL to your preferences (like project-scoped mode and read-only mode).

Security reminder#

A friendly reminder to never connect MCP to production data! Supabase MCP was designed from the beginning to assist with app development and shouldn't be connected to production databases. See our post on Defense in Depth for MCP Servers.

More info#

Read more about all the features in the Remote MCP blog post!