Specific implementation researched
Supabase MCP
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Supabase
- Publisher
- Supabase
- Origin
- Officially from the named publisher
- Deployment mode
- Remote
- Transport
- HTTP
- Authentication
- Browser-based login and authorization for a Supabase organization; a PAT is not required for this workflow.
- Read capabilities
- List tables and migrations · Read logs and advisors · Search documentation
- Write capabilities
- Execute SQL and migrations · Deploy Edge Functions · Manage projects and branches
- Permissions
- Project scope, read_only and feature groups limit tools. Without a selected project, all accessible projects may be reachable.
- Required plan
- According to documentation, branching requires a paid plan; other features may have different requirements.
- Additional costs
- No confirmed information
- Maintenance status
- No confirmed information
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Not verified | — |
| Claude Code | Setup documented | Documentation ↗ |
| Claude Web | Not verified | — |
| Cursor | Setup documented | Documentation ↗ |
Sources & implementation
Supabase MCP Server | Supabase Docs ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://mcp.supabase.com/mcp