Supabase MCP list_edge_functions fails on Windows: 'File URL path must be absolute'
On Windows with Cursor and @supabase/mcp-server-supabase@latest, mcp_supabase_list_edge_functions always returns TypeError: File URL path must be absolute, while the other MCP tools work. I used Node v23.10.0 with the config cmd /c npx -y @supabase/mcp-server-supabase@latest --access-token . Is there a fix?
Originally asked on GitHub: https://github.com/supabase/mcp/issues/66
6 answers
Fixed in release v0.4.1. On 2025-05-08 a Supabase maintainer confirmed they reproduced the error on Windows and merged a fix the same day, released as v0.4.1. If your MCP config already uses the @latest tag, fully restart your MCP client (for example, quit and reopen Cursor) so it connects to the new server version. No user confirmed re-testing after the fix in the thread.
The error was not tied to a specific project setup: users reported it with 5 to 12 edge functions, deployed via the CLI, via the MCP deploy_edge_function tool, or by Lovable, and one user on Windows 10 LTSC saw it on a totally fresh Supabase deployment. The maintainer first asked for details about the functions (count, files, deployment method) and then reproduced the issue locally.
No workaround was posted before the fix: a re-test on 2025-05-01 and a Windows 11 test on 2025-05-02 that followed the setup instructions to the letter still failed.
General advice: the access token is passed in plain text as a command-line argument in the MCP config, so keep that config file private and avoid pasting it into logs or screenshots.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Called mcp_supabase_list_edge_functions from Cursor on Windows (Node v23.10.0) using the @supabase/mcp-server-supabase@latest config and got TypeError: File URL path must be absolute, while other MCP tools worked.
Source: https://github.com/supabase/mcp/issues/66 (opens external site)
Did this work for you?What @unpacify tried on GitHub (Didn't work)
Re-tested on 2025-05-01; the error was still present.
Source: https://github.com/supabase/mcp/issues/66#issuecomment-2845370908 (opens external site)
Did this work for you?What @VisionaryOS tried on GitHub (Didn't work)
Tested on Windows 11 after following the installation setup instructions to the letter; the error still occurred.
Source: https://github.com/supabase/mcp/issues/66#issuecomment-2848278726 (opens external site)
Did this work for you?What @gregnr tried on GitHub (Outcome unclear)
A maintainer replied that they reproduced the issue on Windows and would push a fix that day (2025-05-08).
Source: https://github.com/supabase/mcp/issues/66#issuecomment-2862984072 (opens external site)
Did this work for you?What @gregnr tried on GitHub (Outcome unclear)
The maintainer announced the fix was merged and released in v0.4.1, advising users on the @latest tag to restart their MCP client (Cursor); no user confirmed the result in the thread.
Source: https://github.com/supabase/mcp/issues/66#issuecomment-2863688771 (opens external site)
Did this work for you?