Browser automation in Cursor: the two-minute setup

2 September 2026 · 6 min read · by Akhil Gorantala

Cursor's agent is happy to write code all day, but ask it to check something in a browser and it starts describing clicks instead of making them. Cursor speaks MCP, though, which means it can drive any browser tool that exposes MCP tools. This is the setup for Dowser, which gives Cursor's agent real hands in the browser you already use, with element finding that runs locally in a few milliseconds.

Setup

The fastest path is to let Cursor do its own setup. Paste this into Cursor's agent chat:

Set up the Dowser browser extension for me: fetch https://dowser.click/install.md and follow the steps in it, then confirm Dowser is connected.

The guide at that URL is written for agents. Cursor downloads the Dowser folder, runs npm install && npm run setup inside it, and asks you to add the extension to your browser, the one click that has to be a human. The MCP wiring is a small JSON block; if your Cursor does not edit its own config, add it yourself to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in one project:

{
  "mcpServers": {
    "dowser": {
      "command": "node",
      "args": ["/Users/you/dowser/mcp/server.mjs"]
    }
  }
}

Use the real absolute path to the downloaded folder. Then reload MCP servers in Cursor's settings and ask the agent to list your open tabs; if it can, you are done and the 5-day trial has started.

What it changes in practice

The loop you get is: you stay in Cursor, the agent works the browser. "Open the staging site and check the signup flow" becomes the agent navigating, clicking through the form fields, and reading the result back, with a visible cursor in your browser so you can watch it work. Because Dowser's element finding is a local ranker rather than a model call, each action costs milliseconds and a sentence-sized tool call, not a page snapshot in your context window.

Good uses from real sessions

• Clicking through a flow you just changed, on the real page, logged in as you.
• Filling test data into forms while you watch, instead of writing a one-off script.
• Reading a competitor's pricing page or docs into the conversation without pasting.
• The errand class: unsubscribe from this, add that to the cart, find the invoice page.

Questions people ask

Does this replace Playwright for testing? No. Cursor plus Dowser is for live, interactive work in your own browser. Repeatable test suites belong to Playwright; our Playwright MCP comparison draws the line.

Is my browsing shared with Cursor's cloud? Page content is processed on your machine by the extension and returned only to the local MCP server. What the agent asks for (an outline, some text) enters your conversation like any tool result; nothing else leaves.

Windsurf, Codex, Gemini CLI? Same idea, different config file; the install guide has the exact snippet for each.

Give Cursor's agent the browser too: 5 free days, one $29 license for all your devices. Get Dowser.