Home › Clients › Cursor › Browser Automation

Cursor: Browser Automation

Cursor setup for Browser Automation. 5 indexed servers in this category, 1 with a remote endpoint. Named here: Browser Use, Playwright (Microsoft), SeleniumBase MCP. Cursor reads MCP servers from mcp.json in the project or the user config. The file shape on the Cursor hub is quoted from Cursor's docs. The Cursor block on each server page is generated from that server's registry packages and remotes.

Category hub: Browser Automation. The same category for Claude and VS Code.

Paid listings (Sponsored, then Featured) appear first in every list, marked Advertisement. Organic listings follow, sorted by GitHub stars. Sorted by GitHub stars as of 2026-10-17. Servers with no public GitHub repo follow, in alphabetical order.

• Browser Use — stdio (local, pypi). Browser Use's server for driving a Chrome browser through multi-step tasks such as forms and data extraction. · ★ 118,324 GitHub stars · 2026-10-17
• Playwright (Microsoft) — stdio (local, npm). Microsoft's server that drives a real browser with Playwright so agents can navigate and interact with pages. · ★ 38,283 GitHub stars · 2026-10-17
• SeleniumBase MCP — stdio (local, pypi). SeleniumBase MCP is Seleniumbase's MCP server in the official registry (io.github.seleniumbase/seleniumbase). Declared transport: stdio (local, pypi). · ★ 13,085 GitHub stars · 2026-10-17
• Browserbase — stdio (local, npm). Controls cloud-hosted browsers through Browserbase and Stagehand for web automation. · ★ 3,399 GitHub stars · 2026-10-17
• Browserless — Streamable HTTP (remote), stdio (local, npm). Browserless's server for browser automation, scraping, screenshots, and PDFs. A remote endpoint and a package are both declared. · ★ 8 GitHub stars · 2026-10-17