browserbase / browse-plugin

The local plugin runs an MCP server over stdio that wraps Playwright, exposing 10 MCP tools — navigate, click, type, snapshot, screenshot, scroll, evaluate, select, wait, and close — against a real, visible Chrome window, with cookies and login state carried over through a persistent Chrome profile. It needs no API key. The cloud plugin instead deploys serverless browser automation to Browserbase's own infrastructure through its bb CLI, and is what a reader actually needs for stealth browsing, rotating proxies, or CAPTCHA solving, none of which the local plugin can do.

This is built specifically for the Cursor IDE Marketplace, not for a general agent-skills setup — installing it gives Cursor's model direct control of a browser through plain-language requests like "go to Hacker News and get the top 5 stories." The cloud plugin only matters once a reader is willing to create a Browserbase account and set BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID; without those two variables, only the free local plugin does anything.

READ THE FULL ANALYSIS＋

Both live skills carry an "unverified" dependency label in our data, so the requirements above are read from the README rather than confirmed against the skill files themselves — including the claim that the local plugin needs nothing but a Chrome install. The repository also lists no license in our capture.

A third row exists for this repository but is dead — an entry named "Browserbase Skills" with no content of its own — and is not counted or described above.