The agent cannot access the network and the browser console, which opens inside the cursor as a separate tab

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

If you ask the agent for console and network information from the browser opened in the cursor, it responds, “cursor-ide-browser is the only MCP that works with the built-in Cursor browser. It has browser_console_messages and browser_network_requests, but they return a response in an unprocessable format (Unsupported content type “metadata”). This appears to be a bug or implementation limitation.”

Steps to Reproduce

open a browser and ask for access to the console and network

Operating System

Linux

Version Information

Version: 2.5.20 (user setup)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. It looks like this is a bug in how browser_console_messages and browser_network_requests return their responses. The “Unsupported content type metadata” error means the agent can’t parse the data those tools are sending.

A couple things to check while we look into it:

  1. Do other browser tools work correctly (navigate, click, screenshot)? Or is your whole browser MCP broken?
  2. Go to Settings > Tools & MCP > Browser Automation. Turn the toggle off, wait 10 seconds, then turn it back on. Fully restart Cursor (not just Reload Window), then try again in a new chat.

If it still doesn’t work, please share the Request ID from the failed chat (three dots in the top right of the chat > Copy Request ID) so the team can investigate what’s happening on the server side.

  1. Navigation, clicks, and screenshots are working. The browser bar is working.

  2. I did it, but the error persists.

  3. 870cfc74-2302-4bde-867c-b03c1ee175f9 - Request ID:

    Calling browser_network_requests for this tab returns the error “Unsupported content type ‘metadata’.” This may be a limitation or a bug in the current implementation of the MCP tool.

Hey there!

I can confirm this is a bug, and I’ve filed a ticket for it. Thanks for the report. :folded_hands:

You may find it useful to try some other Browser MCP servers if this is critical for you, like playwright or chrome-devtools-mcp!