← Back to directory

BrowserOS MCP Server

Community

MCP server exposing Chromium browser automation capabilities through BrowserOS

GitHub source repository ↗

★ 13.4k Stars Category · Browser Very popular Source revision 068f4c692149

34FMRS · D

Reliability

4/20

Security and permissions

5/20

Maintenance

10/20

Documentation

8/20

Setup experience

7/20

BrowserOS MCP Server is an official MCP server providing AI agents with local browser automation, reusing real login sessions, supporting parallel tasks and session replay. Compared to cloud browsers and headless drivers, it emphasizes privacy and user control. Suitable for developers handling real workflows, but requires caution regarding agent permissions and potential risks.

Read the FMRS scoring method →

BrowserOS MCP Server is a Model Context Protocol (MCP) server that exposes Chromium browser automation capabilities through the BrowserOS platform. It allows AI agents such as Claude Code, Codex, Cursor, and others to control the BrowserOS neo browser via the MCP protocol, leveraging real login sessions, parallel task execution, live monitoring, and session replay. Developed by the BrowserOS team, it is part of the BrowserOS open-source project.

Tools

The tool list has not been reviewed yet.

Setup

Install BrowserOS neo and import your logins from Chrome in one click, along with bookmarks and extensions. Then, in BrowserOS neo, connect your AI tools with one click (Claude Code, Codex, Cursor, VS Code, Zed, OpenCode, Antigravity) or via URL for any MCP client. For Claude Desktop, use the provided drop-in extension.

Fit and risk

Best for

Developers who need agents to automate real workflows in logged-in sessions (e.g., personal email, social media, CRM)
Users who prefer local browser automation with data privacy
Those who need to run multiple AI agents in parallel and monitor their activity

Not for

CI/CD testing in stateless, login-free environments (use Playwright or browser-use instead)
Users who prefer cloud browser services over local execution
Those who don't need browser automation or only need simple web scraping

Required permissions

Read and import browser logins (from Chrome)
Access user browser sessions for agent automation
Store session recordings, screenshots, and history locally under ~/.browserclaw/
Send anonymous product usage events (agent connect/disconnect, version, OS) – never URLs, page content, prompts, tool results, or screenshots

Risks and side effects

Agents use your real login sessions and may perform unintended actions (e.g., sending emails, posting content) – approve with caution
Malicious prompts could lead to sensitive data exposure or unauthorized actions
Although data is stored locally, inherent risks of browser automation (e.g., mis-clicks, form errors) remain
Open-source version is AGPL-3.0 licensed, which may not suit all commercial use cases

Troubleshooting

Ensure BrowserOS neo is installed and running
Verify the agent is correctly connected to the MCP endpoint (often a local address)
If agents can't access logins, confirm import from Chrome and granted permissions
Check official docs (docs.browseros.com/neo) or seek help on Discord/Slack
Update BrowserOS neo or MCP server to the latest version

Use cases

Let AI agents book flights and restaurants

Unsubscribe from junk email

Find apartments and message landlords

Reply on X, queue posts, pull engagement numbers

Update your CRM, file expenses, pull reports from internal tools

Supported clients

Claude DesktopFull support

Claude CodeFull support

CodexFull support

CursorFull support

VS CodeFull support

ZedFull support

OpenCodeFull support

AntigravityFull support

Related MCP servers

Compare with other MCP servers