Supabase MCP get_logs returns empty array for edge function logs — workaround?
Using the supabase/mcp get_logs tool with service=edge-function, I get {"result":[],"error":null} immediately after an edge function runs, even though the function is executing and service=postgres returns logs fine. This is on macOS 24.4.0 with the latest supabase-js. Is this a known bug, and is there a way to see edge function logs through MCP?
Originally asked on GitHub: https://github.com/supabase/mcp/issues/54
4 answers
Still open: no fix or maintainer response is recorded in the thread; the last comment (2026-08-04) shows the behavior still occurs in a narrower form.
The original reporter consistently got {"result":[],"error":null} from get_logs with service=edge-function while service=postgres worked, so the problem is specific to the edge-function log surface. The only confirmed workaround in the thread is to bypass MCP for these logs: one commenter used browser MCP in Cursor to open the function in the Supabase Dashboard, locate the refresh button, and read the logs from the browser UI.
A later reproduction after OAuth reauthorization found that get_logs for edge-function returned a non-empty response of about 37 KB, but it contained invocation-level records and omitted a custom console.info event that the Dashboard showed for the same invocation. That suggests the MCP edge-function surface may return invocation-only evidence, not full execution/console logs.
Practical status: use the Supabase Dashboard (or browser-based access) to debug edge function logs; if you rely on get_logs, expect invocation-level data at best. As general advice, verify with the Dashboard whether the missing entries are custom console messages rather than invocation records.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
After deploying and triggering an edge function, called get_logs with service=edge-function and got {"result":[],"error":null}; service=postgres returned logs normally in the same project.
Source: https://github.com/supabase/mcp/issues/54 (opens external site)
Did this work for you?What @skamensky tried on GitHub (Worked)
Switched to browser MCP in Cursor, opened the function in the Supabase Dashboard, found the refresh button, and read the logs from the UI.
Source: https://github.com/supabase/mcp/issues/54#issuecomment-2925551569 (opens external site)
Did this work for you?What @makhataibar tried on GitHub (Partly worked)
After OAuth reauthorization, called get_logs for API, PostgreSQL, branch-action, and edge-function; the edge-function response was non-empty (~37 KB) but omitted the custom console.info event visible in the Dashboard for the same invocation.
Source: https://github.com/supabase/mcp/issues/54#issuecomment-5175144507 (opens external site)
Did this work for you?