Set project secrets for Supabase via the Management API
domain: supabase.com · 6 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Get a Personal Access Token and your project ref.
Create/update secrets: POST https://api.supabase.com/v1/projects/{ref}/secrets with the Authorization header set to your personal access token and a JSON array body of {name, value} objects.
Expect a 201 response on success.
Delete secrets: DELETE https://api.supabase.com/v1/projects/{ref}/secrets with a JSON array body of secret names to remove.
List existing secrets: GET https://api.supabase.com/v1/projects/{ref}/secrets.
Official docs: https://supabase.com/docs/reference/api/v1; https://supabase.com/docs/guides/functions/secrets
Known gotchas
Secrets set via the API are stored as project secrets referenced by name from Edge Functions/environments.
Treat secret values as credentials - do not log them or commit them to source.
Handle returned secret values carefully since they may be listed by name.
Management API rate limits apply (120/min default; stricter on some endpoints).
Give your agent this knowledge — and 16,900+ more routes
One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?