send_management_api_request

MCP tool from Supabase MCP Server by alexander-zuev

Sends arbitrary requests to Supabase Management API with auto-injection of project ref

How to use it

send_management_api_request is exposed by the Supabase MCP Server MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the send_management_api_request tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Supabase MCP Server

$pipx install supabase-mcp-server

FULL SUPABASE MCP SERVER LISTING

Other tools in Supabase MCP Server (26)

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 a new user

Delete a factor on a user (currently not implemented in SDK)

Delete a user by their ID

Schema changes (DROP, CREATE) - require unsafe mode + confirmation

execute_postgresql

Executes SQL statements against your database

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

Lists schemas with sizes and table counts

get_table_schema

Gets detailed table structure (columns, keys, relationships)

Lists tables, foreign tables, and views with metadata

Retrieve a user by their ID

invite_user_by_email

Send an invite link to a user's email

List all users with pagination

live_dangerously

Toggles between safe and unsafe modes

and recovery links require the user to already exist in the system

retrieve_migrations

Gets migrations with filtering and pagination options

Read-only operations (SELECT) - always allowed

links don't require the user to exist

State-changing operations (POST, PUT, PATCH, DELETE) - require unsafe mode

update_user_by_id

Update user attributes by ID

Data modifications (INSERT, UPDATE, DELETE) - require unsafe mode