Browser MCP

Maintains Browser MCP’s local server and Chrome extension, connecting coding agents to approved existing browser profiles.

About Browser MCP

The BrowserMCP organization maintains the Browser MCP server and companion Chrome extension. Their shared purpose is letting AI applications operate a real browser profile through a deliberately paired local connection.

Browser MCP joins an agent client to an existing Chrome profile through an MCP server and browser extension. The extension mediates pairing and browser commands; task tabs give the agent a place to work while the browser controls remain available to the user. This is useful when an approved task depends on an already signed-in account.

The name describes this project, not every browser MCP implementation. Verify the organization, package, extension, and matching documentation together before granting a coding agent access to a signed-in browser.

Software from Browser MCP

Choose this route when the task depends on an existing Chrome profile. The guide explains how the server and extension connect that profile to an agent.

Browser MCP
Connect a local MCP server and Chrome extension so an agent can use your existing browser profile. Pair the extension deliberately, then work in task tabs with the selected account.
- Deployment, Browser & Desktop
- Browser Automation
- Browser Automation
- MCP

Alternatives to Browser MCP Workflows

Compare CitroLabs for task Spaces in a shared browser, BrowserOS for a browser with external-agent MCP, Microsoft for Playwright MCP automation, PinchTab for profile and instance orchestration. Choose by the browser environment and task result you need.

Frequently Asked Questions

Is Browser MCP a Microsoft project?

No. The linked project is published by BrowserMCP. Microsoft’s Playwright MCP is a different repository and installation path.

What components does the publisher maintain?

The repository includes the MCP server, local daemon, protocol, and Chrome-extension source. They form one browser connection workflow.

Is the extension necessary for real Chrome use?

The documented workflow uses the official extension with the local MCP server. A random browser extension or a server-only config is not equivalent.

Does this publisher supply an official Skill?

The main repository does not document an end-user Skill. The verified entry points are the server, extension, and official configuration documentation.

Can modified copies use the same branding?

Read the source license and branding notes. The project asks published modified extensions or servers to use a different name and icon so they are not confused with the official release.

Where should the connection be verified?

Use the extension’s pairing control and the official client instructions. Confirm the code and browser profile before reading any signed-in account content.

Read One Signed-In Report

A read-only report lookup checks pairing and account context without changing business records. Use it to decide whether the existing Chrome session fits later tasks.

Open Browser MCP guide