Supabase MCP Server
UnclaimedQuery MCP enables end-to-end management of Supabase via chat interface: read & write query executions, management API support, automatic migration versioning, access to logs and much more.
Install
pipx install supabase-mcp-serverUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverTools (27)
blocked
Destructive operations (delete project, etc.) - never allowed
call_auth_admin_method
to directly invoke Auth Admin methods with proper parameter handling
confirm_destructive_operation
Executes high-risk operations after confirmation
create_user
Create a new user
delete_factor
Delete a factor on a user (currently not implemented in SDK)
delete_user
Delete a user by their ID
destructive
Schema changes (DROP, CREATE) - require unsafe mode + confirmation
execute_postgresql
Executes SQL statements against your database
generate_link
Generate an email link for various authentication purposes
get_auth_admin_methods_spec
to retrieve documentation for all available Auth Admin methods
get_management_api_safety_rules
Gets all safety rules with human-readable explanations
get_management_api_spec
Gets the enriched API specification with safety information
get_schemas
Lists schemas with sizes and table counts
get_table_schema
Gets detailed table structure (columns, keys, relationships)
get_tables
Lists tables, foreign tables, and views with metadata
get_user_by_id
Retrieve a user by their ID
invite_user_by_email
Send an invite link to a user's email
list_users
List all users with pagination
live_dangerously
Toggles between safe and unsafe modes
magiclink
and recovery links require the user to already exist in the system
retrieve_migrations
Gets migrations with filtering and pagination options
safe
Read-only operations (SELECT) - always allowed
send_management_api_request
Sends arbitrary requests to Supabase Management API with auto-injection of project ref
signup
links don't require the user to exist
unsafe
State-changing operations (POST, PUT, PATCH, DELETE) - require unsafe mode
update_user_by_id
Update user attributes by ID
write
Data modifications (INSERT, UPDATE, DELETE) - require unsafe mode