Selfhosted Supabase
The Self-Hosted Supabase MCP server provides a bridge between MCP clients and self-hosted Supabase instances, enabling database introspection and management directly from development environments. Built from scratch by HenkDz, it offers tools for querying database schemas, managing migrations, inspecting connections, handling auth users, and interacting with storage buckets through a streamlined interface focused on single-project environments. Unlike the official cloud server, this implementation avoids multi-project complexities while maintaining core functionality through both RPC calls and direct database connections, making it ideal for developers working with local or privately hosted Supabase projects.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- database
- Source
- PulseMCP
- Repository
- github.com/henkdz/selfhosted-supabase-mcp
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Selfhosted Supabase from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.