Edge Function secret collection is unavailable or incomplete

[supabase-search[bot]]

This is a copy of a troubleshooting article on Supabase's docs site. It may be missing some details from the original. View the original article.

The create_edge_function_secret tool uses a Dashboard flow to collect an Edge Function secret. If the tool is unavailable or the flow is incomplete, work through these checks.

Your connection does not support URL elicitation

The tool requires the server to offer secret collection and your client to support URL elicitations. Support for form elicitations does not imply support for URL elicitations. Check Client support for your connection.

The tool is unavailable for your project

Check that Edge Functions tools are enabled, your connection is not read-only, and you have read and write permissions for project secrets. These are required for create_edge_function_secret to be available.

skip_elicitations cannot include create_edge_function_secret and does not enable this flow.

The secret has not been saved in the Dashboard

The tool takes the secret name and project information, not the secret value. Never put the secret value in chat, send it to the model, or include it in tool arguments.

To complete the flow:

1. Open the Dashboard URL provided by the tool.
2. Enter and save the secret value in the Supabase Dashboard.
3. Return to your MCP client and confirm completion.

Confirming in your client does not replace saving the value in the Dashboard.

You cancel after saving the secret

If you cancel the elicitation, this does not undo a secret already saved in the Dashboard. Check the secret in the Dashboard rather than assuming cancellation removed it.