Why won't browser-tools-mcp connect in Cursor 1.2.4 after reinstall?

Question

After reinstalling browser-tools-mcp, the MCP server no longer connects in Cursor 1.2.4, even though the browser extension and the server process are running normally. I tried both the args-array config and the single-string npx config, pinning the version to @1.2.0, and Cursor still shows no connection. What mcp.json configuration works for this setup?

Originally asked on GitHub: https://github.com/AgentDeskAI/browser-tools-mcp/issues/204

AgentArmor team · Accepted Answer

Resolved by configuration — the thread is closed and the working setup is the args-array form of the npx command. One commenter reported that pinning the version to `@1.2.0` was the problem, and that this is the correct config:

```json
{
  "mcpServers": {
    "browser-tools": {
      "command": "npx",
      "args": ["-y", "@agentdeskai/browser-tools-mcp"]
    }
  }
}
```

Other commenters reported the pinned version also connects: `args: ["-y", "@agentdeskai/browser-tools-mcp@1.2.0"]`, and the original pin without `-y`. The reporter's own attempts — the args-array form without `-y` and the single-string form `"command": "npx @agentdeskai/browser-tools-mcp@1.2.0"` — did not connect in Cursor 1.2.4.

General advice: after editing the config, restart Cursor so the client reloads the MCP server list before checking the connection.

AgentArmor team · Answer

**What @rafaelnogueira1 tried on GitHub** (Worked)

Used `command: "npx"` with `args: ["-y", "@agentdeskai/browser-tools-mcp"]` (no version pin). The commenter said this is the correct way and that the problem was pinning `@1.2.0`.

Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/204#issuecomment-3201544045

AgentArmor team · Answer

**What @chrisedington tried on GitHub** (Worked)

Kept the pinned `@1.2.0` version but added the `-y` flag to the npx args. The commenter reported this fixed the connection.

Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/204#issuecomment-3191190933

AgentArmor team · Answer

**What @Bensigo tried on GitHub** (Worked)

Used the args-array form with the pinned `@1.2.0` version and no `-y` flag. A commenter reported this works.

Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/204#issuecomment-3097078235

AgentArmor team · Answer

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

Used `command: "npx"` with `args: ["@agentdeskai/browser-tools-mcp@1.2.0"]` (no `-y`). The reporter said Cursor still did not connect.

Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/204

AgentArmor team · Answer

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

Used the whole npx invocation as a single command string, `"command": "npx @agentdeskai/browser-tools-mcp@1.2.0"`. The reporter said Cursor still did not connect.

Source: https://github.com/AgentDeskAI/browser-tools-mcp/issues/204

Why won't browser-tools-mcp connect in Cursor 1.2.4 after reinstall?

6 answers

Add your answer or comment

Why won't browser-tools-mcp connect in Cursor 1.2.4 after reinstall?

6 answers

Add your answer or comment

Related questions