home / mcp / supabase mcp http stream server for n8n mcp server

Supabase MCP HTTP Stream Server for n8n MCP Server

Provides an HTTP stream transport MCP server enabling real-time Supabase operations with n8n and AI agents.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "bifrotek-com-supabase-mcp-http-stream-n8n": {
      "url": "https://your.domain.com:3333/mcp",
      "headers": {
        "DOMAIN": "your.domain.com",
        "MCP_PORT": "3333",
        "NODE_ENV": "production",
        "MCP_API_KEYS": "YOUR_API_KEYS",
        "MCP_FEATURES": "database,docs,development,functions",
        "MCP_READ_ONLY": "false",
        "SUPABASE_PROJECT_REF": "YOUR_PROJECT_REF",
        "SUPABASE_ACCESS_TOKEN": "YOUR_SUPABASE_ACCESS_TOKEN",
        "MCP_RATE_LIMIT_GENERAL": "60",
        "MCP_RATE_LIMIT_REQUESTS": "100"
      }
    }
  }
}

You are running an HTTP Stream MCP server that connects Supabase with modern automation tools like n8n. This server exposes a real-time HTTP transport for executing MCP tools, managing sessions, and querying data, enabling you to build responsive automation flows and AI-driven interactions around your Supabase project.

How to use

Use the HTTP Stream transport to interact with your Supabase MCP server from an MCP client. Start sessions, send JSON-RPC style tool requests, and receive responses over the HTTP stream endpoint. This flow is designed for real-time automation scenarios such as interactive AI agents, workflow orchestration in n8n, and dynamic data operations against your Supabase project.

How to install

Prerequisites you need before installing: a Linux or macOS environment, Docker and Docker Compose, and a domain with TLS termination configured for secure access.

1. Create a project directory for your MCP server and download the deployment files.

2. Set up environment variables for Supabase access and MCP configuration.

3. Start the server using Docker Compose and verify the HTTP endpoint becomes available on port 3333.

Exact commands you will run are shown in the steps below. Replace placeholder values with your own credentials and domain.

Additional sections

Configuration governs how the MCP server authenticates, routes requests, and enforces security. You can tune rate limits, allowed origins, and feature groups to tailor the server to your environment.

Security is built around API keys, TLS, and strict input validation. Enable API keys, restrict origins, and keep your tokens securely stored. You can also enable read-only mode for safer environments.

Notes and tips: use the HTTP Stream transport for best reliability. If you encounter compatibility issues with legacy clients, you can fall back to SSE, but HTTP Stream offers more robust error handling and stability for modern tools.

Troubleshooting tips include checking startup logs for readiness messages, verifying that TLS termination is functioning, and ensuring the domain and port are accessible from your MCP client.

Available tools

list_tables

Lists all database tables available in the connected Supabase project.

list_extensions

Lists installed database extensions for the project.

execute_sql

Executes raw SQL queries against the connected database.

apply_migration

Applies database migrations to update the schema.

search_docs

Searches Supabase documentation programmatically.

list_edge_functions

Lists Edge Functions deployed in the project.

deploy_edge_function

Deploys an Edge Function to the project.

get_project_url

Retrieves the API URL for the current project.

get_anon_key

Retrieves the anonymous API key for client usage.

generate_typescript_types

Generates TypeScript types from database schema.

list_migrations

Lists database migrations that have been applied or are pending.