BrowserMCP Shows '0 Tools Enabled' in Cursor 1.1.6 Despite Config
Using @browsermcp/mcp@latest with Cursor 1.1.6 on macOS 15.5 (Node v20.18.1), the MCP server shows as Enabled in Cursor's MCP settings but displays '0 tools enabled', and no browser_* tools appear. The Chrome/Brave extension shows Connected and .cursor/mcp.json uses npx with @browsermcp/mcp@latest. Restarts, refreshing the MCP tab, and config validation don't help. Why are no tools registered, and what actually fixes it?
Originally asked on GitHub: https://github.com/BrowserMCP/mcp/issues/82
6 answers
The issue is still open (as of the thread's last comment in July 2025); no maintainer fix is posted. The suspected cause (comment 7) is that Cursor no longer downloads the package itself when the config uses
npx, so the server never actually starts.Workaround that worked (comment 8): install the package globally and point Cursor directly at the installed file.
bashnpm install -g @browsermcp/mcp@latest npm root -g # prints the global node_modules pathThen set the Cursor config to run that file with
node, e.g. on Windows:json{ "mcpServers": { "browsermcp": { "command": "node", "args": ["C:\\nvm4w\\nodejs\\node_modules\\@browsermcp\\mcp\\dist\\index.js"] } } }Use the path
npm root -gprints on your machine, then fully restart Cursor.Simpler variant that also worked (comment 9): the package's
package.jsondefines a bin namedmcp-server-browsermcp. After the global install, use:json{ "mcpServers": { "browsermcp": { "command": "mcp-server-browsermcp" } } }One user also reported that
npx --yes clear-npx-cachesolved it (comment 10). Dropping@latestfrom the npx args ("args": ["@browsermcp/mcp"]) was suggested as a temporary fix (comment 4), but another user said it still didn't work.General advice: run the exact command from your config in a terminal first; if it fails there, Cursor will report 0 tools too.
Did this work for you?What @akromicc tried on GitHub (Worked)
Installed @browsermcp/mcp globally, used
npm root -gto find the installed path, and configured Cursor to run it withnodepointing atdist/index.js, then fully restarted Cursor. Tools loaded correctly.Source: https://github.com/BrowserMCP/mcp/issues/82#issuecomment-3040083606 (opens external site)
Did this work for you?What @seinho-code tried on GitHub (Worked)
Installed @browsermcp/mcp globally and set the Cursor config command to the package's bin name
mcp-server-browsermcp(found in package.json), with no args.Source: https://github.com/BrowserMCP/mcp/issues/82#issuecomment-3055016090 (opens external site)
Did this work for you?What @CHristopherkeith tried on GitHub (Worked)
Ran
npx --yes clear-npx-cacheto clear the npx cache.Source: https://github.com/BrowserMCP/mcp/issues/82#issuecomment-3094443827 (opens external site)
Did this work for you?What @nic269 tried on GitHub (Partly worked)
Changed the MCP config args from
@browsermcp/mcp@latestto just@browsermcp/mcpto avoid a suspected bad latest version; claimed temporary fix, but another user later reported it still didn't work.Source: https://github.com/BrowserMCP/mcp/issues/82#issuecomment-3024607510 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Reporter fully restarted Cursor, verified the extension showed Connected in Chrome and Brave, refreshed the MCP tab, checked Node version and config JSON validity, and tried both browsers.
Source: https://github.com/BrowserMCP/mcp/issues/82 (opens external site)
Did this work for you?
Related questions
- Why are workspace packages missing from BrowserMCP and does its extension send telemetry?
- BrowserMCP clicks fail with 'Error: No tab with given id' in Claude Desktop and Claude Code
- BrowserMCP fails to start: 'Failed to kill process on port 9009' when port 9009 is free
- browser_click times out on PubMed filters (WebSocket response timeout after 30000ms)
- BrowserMCP browser_get_console_logs returns empty after browser_navigate or refresh?