BrowserMCP clicks fail with 'Error: No tab with given id' in Claude Desktop and Claude Code
Using BrowserMCP (BrowserMCP/mcp) with Claude Desktop and Claude Code, clicks on buttons and input fields fail roughly 50% of the time. The mouse hovers over the element but the click never lands, and Claude returns 'Error: No tab with given id 515612901.' It happens on sites like Twitter, and one user on a MacBook saw it with only one tab open in Chrome. Is there a known fix or workaround?
Originally asked on GitHub: https://github.com/BrowserMCP/mcp/issues/56
6 answers
Status: still open. As of the last comment in this thread (June 3, 2025), no maintainer fix or root cause had been posted; a contributor asked for a screen recording or a reproducible example.
The only workaround in the thread that worked for someone: a commenter with the same problem switched from a Chromium-based browser (Brave or Opera) to default Google Chrome. Another commenter replied that they already use standard Chrome, and a commenter on a MacBook using Claude Code with default Chrome and a single tab open still hit the error even though
/mcpshowed the server connected.The reported error is
Error: No tab with given id <number>. In Claude Desktop it appears after an element reference like{"ref": "s2e245", "element": "Post text textbox"}when composing a tweet on Twitter; in Claude Code it appears afterbrowsermcp:browser_type (MCP)(element: "Email textbox", ref: "s1e21", ...)followed by the same error.General advice if you hit this: keep the Chrome profile and window that BrowserMCP controls open for the whole session, don't close or refresh the tab mid-task, and rule out Chrome extensions that might intercept clicks. If it still fails, reproduce it on a minimal page and file an issue with the exact prompt, browser version, and the tab ID from the error.
Did this work for you?What @chaarlie130 tried on GitHub (Worked)
A commenter who had the same problem switched from a Chromium-based browser (Brave or Opera) to default Google Chrome and reported that clicking worked again.
Source: https://github.com/BrowserMCP/mcp/issues/56#issuecomment-2907650095 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
The reporter used BrowserMCP with Claude Desktop and observed clicks failing about 50% of the time on buttons and input fields; no fix was attempted in the initial report.
Source: https://github.com/BrowserMCP/mcp/issues/56 (opens external site)
Did this work for you?What @haenswoerst tried on GitHub (Didn't work)
A commenter reproduced the failure on Twitter ('compose a tweet'): the mouse hovered over the input field but the click failed, and Claude returned 'Error: No tab with given id 515612901.'
Source: https://github.com/BrowserMCP/mcp/issues/56#issuecomment-2907903419 (opens external site)
Did this work for you?What @isi2010 tried on GitHub (Didn't work)
A Claude Code user on a MacBook with default Chrome and only one tab open got 'Error: No tab with given id 24961936' even though /mcp showed the server connected; no resolution was posted.
Source: https://github.com/BrowserMCP/mcp/issues/56#issuecomment-2936709698 (opens external site)
Did this work for you?What @haenswoerst tried on GitHub (Outcome unclear)
In response to the browser-switch workaround, a commenter stated that they already use standard Chrome.
Source: https://github.com/BrowserMCP/mcp/issues/56#issuecomment-2907904897 (opens external site)
Did this work for you?
Related questions
- Why are workspace packages missing from BrowserMCP and does its extension send telemetry?
- BrowserMCP fails to start: 'Failed to kill process on port 9009' when port 9009 is free
- BrowserMCP Shows '0 Tools Enabled' in Cursor 1.1.6 Despite Config
- browser_click times out on PubMed filters (WebSocket response timeout after 30000ms)
- BrowserMCP browser_get_console_logs returns empty after browser_navigate or refresh?