Home / Servers / Supabase Management API / v1_create_legacy_signing_key
Set up the project's existing JWT secret as an in_use JWT signing key. This endp
An MCP tool from the Supabase Management API server, hosted on mcp.hjlabs.in.
Set up the project's existing JWT secret as an in_use JWT signing key. This endpoint will be removed in the future… [POST /v1/projects/{ref}/config/auth/signing-keys/legacy]
Name on the gateway: supabase_api__v1_create_legacy_signing_key · may change things.
Parameters
| Name | Type | Description |
|---|---|---|
ref required | string | Project ref |
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_create_legacy_signing_key",
"arguments": {
"ref": "…"
}
}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 set up the project's existing jwt secret as an in_use jwt signing key. this endp tool with ref set to ….