AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoin s/browsermcp-mcpNeeds helpSolved

    BrowserMCP browser_get_console_logs returns empty after browser_navigate or refresh?

    I'm using BrowserMCP v1.3.4 with Cursor on macOS. browser_get_console_logs always returns an empty result even when the page has console errors. It only returns console info right after connecting; after a browser_navigate or refresh it returns nothing again, so I can't verify in one session whether my code fix removed the console error. Is there a fix or workaround?

    Originally asked on GitHub: https://github.com/BrowserMCP/mcp/issues/69

    4 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Status: open. As of August 2025 this thread has no maintainer response, fix, or verified workaround. The report is for BrowserMCP v1.3.4 on Cursor (macOS), and several users (comments 2 through 7) confirm the same behavior.

      The reporter's testing shows that browser_get_console_logs returns the page's console output only when it is called immediately after establishing the connection (right after clicking Connect). After that, performing a browser_navigate or refreshing the page causes subsequent calls to return an empty result, even when the page actually has console errors.

      Because of this, the intended workflow — navigate to a page, read the console errors, fix the code, refresh, then read the console errors again to confirm the fix within one connection — fails on the second read.

      The thread does not explain why this happens and does not provide a confirmed workaround. Note that refreshing the page is not a way to get the logs back; per the reporter, a refresh after connecting is exactly the step after which the tool stops returning console information. Re-establishing the connection was not tested as a workaround in this thread, so any such suggestion is unverified.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      Reporter on Cursor (macOS) with BrowserMCP v1.3.4 called browser_get_console_logs on a page with console errors and always got an empty result.

      Source: https://github.com/BrowserMCP/mcp/issues/69 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @cwjcwj95 tried on GitHub (Worked)

      The same reporter called browser_get_console_logs immediately after clicking Connect and it returned the page's console information.

      Source: https://github.com/BrowserMCP/mcp/issues/69#issuecomment-2966770136 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @talomaireeni tried on GitHub (Didn't work)

      After connecting, the reporter ran browser_navigate or refreshed the page and called browser_get_console_logs again; it returned empty even though console errors were present.

      Source: https://github.com/BrowserMCP/mcp/issues/69#issuecomment-2994309978 (opens external site)

      Did this work for you?

    Add your answer or comment

See MCP, its grade and setup notesCheck this tool before you install