Give Cursor control of your browser
Cursor writes the change, opens your app, and checks it — in your real browser, with your real session.
Last updated: August 2026
In short
Vibe MCP gives Cursor browser tools through the Model Context Protocol. Add the "vibe" server in Cursor Settings or ~/.cursor/mcp.json, install the Vibe Chrome extension, and Cursor can navigate, click, fill forms, screenshot, and read page content in the browser you are already signed into.
The problem
- Cursor can change your code but cannot see the result in a browser, so you become the manual QA step.
- Headless browsers have no session, so any authenticated page is out of reach.
- Other browser MCP servers break as soon as a second agent connects.
What Vibe MCP changes
- Cursor drives your real Chrome — localhost, staging, or a production dashboard you are logged into.
- Snapshots come back as compact structured content, not megabytes of HTML.
- Multi-agent by design: keep Cursor and your CLI agents connected at once.
Install in 3 steps
1Install the Vibe extension in Chrome
Add Vibe AI Browser from the Chrome Web Store (Chrome, Brave, Edge, or any Chromium browser). This is the piece that lets an agent drive the browser you are already logged into — no second browser profile, no re-authentication.
2Add the Vibe MCP server in Cursor
Open Cursor Settings (Cmd/Ctrl + ,), go to Features → MCP Servers, click Add Server, and paste the config below. You can also edit ~/.cursor/mcp.json directly.
~/.cursor/mcp.jsonjson{ "vibe": { "command": "npx", "args": ["-y", "@vibebrowser/mcp"] } }3Connect the extension and run your first command
Click the Vibe icon, open Settings, and enable "MCP External Control" until the status reads Connected. Then ask your agent to open a page and take a snapshot — it should return the content of your real tab.
Your relay URL / extension UUID grants live control of your browser session. Treat it like a password: never commit it or paste it into a shared chat.
Tools Cursor gets
| Tool | Description |
|---|---|
| navigate_to_url | Navigate to any URL |
| go_back / go_forward | Browser history navigation |
| click | Click elements on the page |
| type / fill | Enter text into inputs |
| scroll | Scroll the page |
| take_screenshot | Capture screenshots |
| get_page_content | Extract page text or HTML |
| get_tabs / create_new_tab / switch_to_tab / close_tab | Tab management |
| keyboard_shortcut | Press keyboard combinations |
| web_search | Search the web |
How it compares
| Feature | Vibe MCP | Playwright MCP | BrowserMCP |
|---|---|---|---|
| Multi-agent support | Yes | No | No |
| Uses your browser profile | Yes | No | No |
| Logged-in sessions | Yes | No | No |
| No separate browser | Yes | No | No |
| Local & private | Yes | Yes | Partial |
| Content-script based | Yes | No | No |
Cursor browser control — FAQ
- How do I add a browser MCP server to Cursor?
- In Cursor, open Settings → Features → MCP Servers → Add Server and add an entry named "vibe" with command npx and args ["-y", "@vibebrowser/mcp"]. Or edit ~/.cursor/mcp.json directly and reload Cursor.
- Can Cursor use my logged-in browser sessions?
- Yes. Vibe works through a Chrome extension in your existing profile, so Cursor acts inside sessions you have already authenticated instead of a clean automation browser.
- How is this different from Playwright MCP in Cursor?
- Playwright MCP launches an isolated browser with no cookies and fails on authenticated flows and multi-agent setups. Vibe uses your real Chrome and supports multiple agents on the same browser at once.
- Does Cursor need to be restarted?
- Reload or restart Cursor after editing the MCP config so the new tools are registered.
Works with your other agents too
The same MCP server powers every client. Multiple agents can drive the same browser at once.
Ready to connect Cursor?
Connecting an agent to your logged-in browser has real privacy consequences. Read what is transmitted, logged and retained in the Privacy Policy.