Cursor Supabase deploy_edge_function
How to: Cursor Supabase deploy_edge_function
Add Supabase to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"mcp-server-supabase": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@supabase/mcp-server-supabase"
],
"env": {
"SUPABASE_ACCESS_TOKEN": "<SUPABASE_ACCESS_TOKEN>"
}
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something deploy_edge_function does. Cursor lists the server's tools on connect and calls deploy_edge_function itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Supabase's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
Supabase will not start until these are set, so deploy_edge_function never becomes available.
-
SUPABASE_ACCESS_TOKEN
Same tool, other clients
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.