Self-Hosted Supabase
Self-hosted Supabase MCP server built from scratch by @abushadab to bridge AI assistants with privately hosted Supabase instances, avoiding the complexities of the official cloud server's multi-project management. The implementation provides 18 tools spanning database operations (SQL execution, schema inspection, migrations), authentication management (user CRUD operations), storage bucket browsing, and TypeScript type generation through both RPC functions and direct PostgreSQL connections. Designed for developers running Supabase via Docker or Coolify who want conversational access to their database schemas, user management, and storage systems without cloud API dependencies, making it valuable for local development workflows and self-hosted production environments.
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
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Self-Hosted 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.