Supabase MCP Server (Self-Hosted)

Community MCP server for managing self-hosted Supabase instances end-to-end — covering database operations, authentication, storage, realtime subscriptions, and database migrations. Variant of Supabase MCP targeting teams running Supabase on their own infrastructure rather than Supabase Cloud.

Evaluated Mar 06, 2026 (0d ago) vcurrent

Homepage ↗ Repo ↗ Databases supabase database postgres auth storage realtime self-hosted mcp-server

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Full DB access via service role key. Implement RLS. Community server — audit before production. Self-hosted security is your responsibility.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

A team running Supabase on self-hosted infrastructure (Docker, Kubernetes) wants AI agents to manage their Supabase instance — database, auth, storage — without going through Supabase Cloud.

Avoid When

You use Supabase Cloud — the official Supabase MCP has better support for cloud features. This variant targets self-hosted deployments specifically.

Use Cases

• Managing self-hosted Supabase database schema and data from backend development agents
• Querying and mutating Supabase PostgreSQL databases from application agents
• Managing Supabase Auth users and permissions from admin agents
• Handling Supabase Storage buckets and files from content management agents

Not For

• Supabase Cloud users (use the official Supabase MCP server instead)
• Teams using other database backends (PostgreSQL-specific)
• Non-Supabase PostgreSQL setups (missing Supabase-specific APIs)

Interface

REST API

Yes

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Authentication

Methods: api_key

OAuth: No Scopes: No

Supabase service role key and self-hosted instance URL required. Service role key has full database access — handle with care.

Pricing

Model: free

Free tier: Yes

Requires CC: No

Supabase self-hosted is free open source. MCP server is free open source. Only infrastructure hosting costs apply.

Agent Metadata

Pagination

cursor

Idempotent

Partial

Retry Guidance

Not documented

Known Gotchas

⚠ Service role key has full database access — treat it like a root credential; never expose to untrusted agents
⚠ Community server (MisterSandFR) — may lag official Supabase API; verify compatibility with your Supabase version
⚠ Self-hosted Supabase version compatibility matters — test against your specific deployment
⚠ Database migrations via agents are irreversible — require human confirmation before running migrations

Alternatives

supabase-mcp-server postgres-mcp-server neon-mcp-server

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Supabase MCP Server (Self-Hosted).

$99

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.