Best for
- Developers and teams using Supabase
- Users wanting to integrate AI into database workflows
S
74FMRS · B
Official server, feature-rich, but requires careful permission and risk management.
The Supabase MCP Server is an official MCP server that enables AI assistants like Cursor, Claude, and Windsurf to interact with the Supabase platform through the Model Context Protocol. It provides tools for managing tables, fetching configuration, querying data, and more. It supports both remote hosted and local CLI environments, with OAuth 2.1 for remote access and read-only mode options.
Tools
The tool list has not been reviewed yet.
Setup
- Read the security best practices. 2. Configure the MCP client. For remote, use the URL https://mcp.supabase.com/mcp. For local CLI, use http://localhost:54321/mcp. The npm package can be run via npx with SUPABASE_ACCESS_TOKEN environment variable, and optional flags like --project-ref and --read-only.
claude_desktop_config.json
{
"mcpServers": {
"supabase": {
"type": "http",
"url": "https://mcp.supabase.com/mcp"
}
}
}
Fit and risk
Not for
- Users not using Supabase
- Scenarios requiring fully local and cloud-free operations (CLI has limited features)
Required permissions
- Requires Supabase access token (SUPABASE_ACCESS_TOKEN)
- May require OAuth 2.1 authorization (remote)
- Read/write by default; read-only mode available (--read-only)
Risks and side effects
- LLM may execute destructive operations such as dropping tables or deleting data
- Token leakage could lead to unauthorized access
- Remote server may log requests, posing privacy concerns
Troubleshooting
- Ensure the access token is valid and not expired
- Verify project reference ID is correct
- Ensure the client supports HTTP transport
- For CLI, check that the local server is running
Use cases
Let AI assistants manage Supabase tables
Query databases using natural language
Fetch project configuration and documentation
Supported clients
Claude DesktopFull support
CursorFull support
WindsurfFull support