MisterSandFR Supabase Mcp Selfhosted
Operate Supabase—database, auth, storage, realtime, and migrations—from your agent when you self-host or run dedicated Supabase stacks.
Overview
Supabase MCP Self-Hosted is a MCP server for the Build phase that lets agents manage self-hosted Supabase across database, auth, storage, realtime, and migrations.
What is this MCP server?
- End-to-end Supabase project management: database, auth, storage, realtime, migrations
- Self-hosted focus for builders running their own Supabase instances
- Smithery-hosted MCP remote; Bearer smithery_api_key authentication
- Package version 1.14.1 from MisterSandFR/Supabase-MCP-SelfHosted on GitHub
- Monitoring-oriented operations described alongside migration workflows
- MCP package version 1.14.1
- 1 Smithery streamable-http remote URL
- 5 Supabase surface areas called out: database, auth, storage, realtime, migrations
Community signal: 7 GitHub stars.
What problem does it solve?
Self-hosted Supabase work splinters across SQL, Auth, Storage, and Realtime UIs, slowing solo builders who already live inside their agent.
Who is it for?
Indie SaaS builders on self-hosted Supabase who want agent-driven schema, auth, storage, and migration tasks with MCP guardrails.
Skip if: Beginners on managed Supabase Free tier who only need occasional SQL without granting broad project admin to an agent.
What do I get? / Deliverables
You can drive Supabase project changes and monitoring queries through MCP tools while keeping infrastructure control on your own stack.
- MCP tools spanning database, auth, storage, realtime, and migrations on your Supabase stack
- Agent-assistable monitoring and migration workflows without manual dashboard hopping
- Versioned server (1.14.1) traceable to GitHub MisterSandFR/Supabase-MCP-SelfHosted
Recommended MCP Servers
Journey fit
Supabase is core product infrastructure for many indie SaaS apps, so the canonical shelf is Build where backends and integrations are assembled. Integrations captures an MCP bridge that lets the agent manage Supabase services instead of you context-switching across dashboards and SQL consoles.
How it compares
Full-stack Supabase admin MCP, not a single-table CRUD skill or a hosted-Postgres-only reader.
Common Questions / FAQ
Who is Supabase MCP Self-Hosted for?
Solo builders and small teams operating self-hosted Supabase who want Claude Code or Cursor to orchestrate database, auth, storage, realtime, and migrations via MCP.
When should I use Supabase MCP Self-Hosted?
Use it during build and operate-style backend work when repeated Supabase admin tasks should run from the agent against your self-hosted project.
How do I add Supabase MCP Self-Hosted to my agent?
Add https://server.smithery.ai/@MisterSandFR/supabase-mcp-selfhosted/mcp as a streamable-http remote with Authorization Bearer {smithery_api_key}, then connect credentials for your Supabase instance per upstream docs.