Home / Servers / Supabase Management API / v1_authorize_user
Authorize user through oauth
An MCP tool from the Supabase Management API server, hosted on mcp.hjlabs.in.
Authorize user through oauth This is an **experimental** endpoint. It is subject to change or removal in future versions. Use it with caution, as it may not remain supported or stable. This endpoint is currently in its **Beta**… [GET /v1/oauth/authorize]
Name on the gateway: supabase_api__v1_authorize_user · read-only.
Parameters
| Name | Type | Description |
|---|---|---|
client_id required | string | client_id parameter |
response_type required | code | token | id_token token | response_type parameter |
redirect_uri required | string | redirect_uri parameter |
scope | string | scope parameter |
state | string | state parameter |
response_mode | string | response_mode parameter |
code_challenge | string | code_challenge parameter |
code_challenge_method | plain | sha256 | S256 | code_challenge_method parameter |
organization_slug | string | Organization slug |
target_flow | string | target_flow parameter |
resource | string | Resource indicator for MCP (Model Context Protocol) clients |
How to call it
Through the Smart Gateway, any client can run it by name with call_tool, or let the gateway find it with search_tools:
{
"name": "supabase_api__v1_authorize_user",
"arguments": {
"client_id": "…",
"response_type": "…",
"redirect_uri": "…"
}
}Or connect the Supabase Management API server directly, which lists 167 tools including this one:
claude mcp add --transport http hj-supabase-api https://mcp.hjlabs.in/mcp/supabase-api \
--header "Authorization: Bearer YOUR_API_KEY"Try asking
Use the authorize user through oauth tool with client_id set to ….