Give GitHub Copilot in VS Code control of your browser
Copilot Chat stops guessing what the page looks like and just opens it.
Last updated: August 2026
In short
Vibe MCP adds browser tools to GitHub Copilot Chat in VS Code. Add the "vibe" server under github.copilot.chat.mcpServers in settings.json, install the Vibe Chrome extension, and Copilot can navigate, click, type, screenshot, and read pages in your real Chrome session.
The problem
- Copilot Chat is confined to your editor and has no view of the running application.
- Anything behind a login is invisible to standard automation tooling.
What Vibe MCP changes
- Copilot gets first-class browser tools that operate on your existing Chrome profile.
- Works alongside other MCP clients connected to the same browser.
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 Vibe to VS Code settings.json
Open your VS Code settings.json and register the Vibe MCP server under Copilot Chat MCP servers, then reload the window.
VS Code settings.jsonjson{ "github.copilot.chat.mcpServers": { "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 VS Code (GitHub Copilot) 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 |
VS Code (GitHub Copilot) browser control — FAQ
- Can GitHub Copilot control a browser?
- Yes, through MCP. Adding the Vibe MCP server to github.copilot.chat.mcpServers in VS Code settings.json gives Copilot Chat browser tools that operate on your real Chrome.
- Does it use my normal Chrome profile?
- Yes. The Vibe extension runs in your existing browser, so Copilot acts inside sessions you are already logged into.
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 VS Code (GitHub Copilot)?
Connecting an agent to your logged-in browser has real privacy consequences. Read what is transmitted, logged and retained in the Privacy Policy.