Pony Browser MCP

Pony Browser MCP connects an MCP client to the user's existing Chrome profile through a loopback-only WebSocket. It adds dedicated agent windows, named task groups, workspace cleanup, and explicit human review prompts to the upstream Browser MCP implementation.

The project has two local components:

1. The Chrome Web Store extension, installed once per Chrome profile and then updated by Chrome.

2. The MCP server, launched on demand by Codex or another MCP client through stdio.

The server intentionally listens only on 127.0.0.1. It is not a shared remote browser service and does not expose browser control on the LAN.

Codex setup

After a release is published:

npm install --global https://github.com/pssrh/pony-browser-mcp/releases/download/v1.0.1/pony-browser-mcp-1.0.1.tgz
codex mcp add pony-browser -- pony-browser-mcp

For shared Windows, macOS, or Linux machines, install the signed extension through the managed-policy scripts in enterprise/. Chrome then checks the GitHub Pages update manifest and upgrades the extension without a Chrome Web Store listing. Developers can still load extension/ unpacked for local testing.

Related MCP server: Real Browser MCP

Build and verify

npm ci
npm test
npm run build:cws

The Web Store ZIP and npm tarball are written to dist/ with SHA-256 files.

Privacy

The extension has no analytics or vendor backend. Browser data requested by an MCP client travels over localhost to that client. The client may then send the data to its configured model provider under the client's own privacy policy. See the full privacy policy.

Attribution

This project is a fork of Browser MCP by Agent360, used under the MIT License. See NOTICE.md and LICENSE.