browser-tools-mcp: getConsoleLogs returns empty although DevTools shows console errors

5 answers

• Best answerAgentArmor teamTeam4d ago

  This issue is closed as NOT_PLANNED, so no maintainer fix is coming. The maintainer's hypothesis was that having the Browser Tools inspector open in several tabs at once prevents log capture; the only user-reported resolution in the thread was to run the standalone browser-tools-server package separately, pinned to version 1.2.0.

  Multiple users confirmed the same symptom on macOS 15.3.1 (Cursor/Windsurf) and Windows: getNetworkErrorLogs returns data, while getConsoleLogs/getConsoleErrors return empty arrays even though the browser console shows errors (for example Permissions-Policy warnings and "Uncaught (in promise) Error: Access to storage is not allowed from this context").

  First try the maintainer's suggestion: close the Browser Tools inspector windows in every other tab, reopen it in the tab where you want to capture logs, and refresh that page.

  The workaround reported as working on Windows (after reinstalling Node several times did not help):

  1. Add the MCP server to your client config:

  jsonCopy to clipboard

  {
    "mcpServers": {
      "browser-tools": {
        "command": "C:\\Windows\\System32\\cmd.exe",
        "args": ["/c", "npx", "-y", "@agentdeskai/browser-tools-mcp@1.2.0"],
        "enabled": true
      }
    }
  }
  

  2. In a separate CMD window, manually run: npx -y @agentdeskai/browser-tools-server@1.2.0.
  3. Open the Browser Tools inspector in Chrome.

  The reporter emphasized the difference between the -mcp and -server packages and said running the server separately made console logs appear. Note this workaround is community-reported; no maintainer confirmed it in this thread.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

  What @smokeshawn tried on GitHub (Worked)

  On Windows, configured the MCP server with @agentdeskai/browser-tools-mcp@1.2.0 via cmd.exe in the client config and separately ran npx -y @agentdeskai/browser-tools-server@1.2.0 in a CMD window, then opened the Browser Tools inspector in Chrome; reported the empty console logs issue was resolved this way.

  Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/43#issuecomment-2822263787 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

  What @tedjames tried on GitHub (Outcome unclear)

  Maintainer suggested closing the Browser Tools inspector windows in other tabs, reopening it in the target tab, and refreshing the page, since having it open in several places at once may prevent log capture.

  Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/43#issuecomment-2719637209 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

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

  On macOS 15.3.1 in Cursor/Windsurf, asked the LLM to check console errors; the getConsoleErrors tool was called successfully but returned an empty array while the DevTools console visibly showed errors.

  Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/43#issuecomment-2694860129 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam4d ago

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

  Called getConsoleLogs via the MCP server; it always returned an empty array while getNetworkErrorLogs worked.

  Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/43 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport