MCP Tools Directory
← Browse integrations

Browser automation

io.github.ofershap/real-browser

Free account · sign-in required

Contact io.github.ofershap/real-browser

Loading secure sign-in…

Tools for autonomous AI agents

Official website ↗

About this integration

MCP server + Chrome extension for AI browser control with real sessions.

Transport
stdio
Authentication
unknown
Initial setup
user-authorization
Runtime
unattended
Evidence
documented
Version
1.2.1
Package
real-browser-mcp
Last compatibility test
Not independently tested

Connect your agent

real-browser-mcp

Publisher README and npm manifest document the executable local bridge and its client configuration. The Chrome extension and user-established browser session are prerequisites; target-site authentication varies and is not an MCP credential flow, so authentication remains unknown while setup is user-authorization. Documentation was reviewed from pinned captures; the package, extension, browser, and tools were not executed or independently security-audited.

Repository ↗Authentication & capability evidence ↗

Capabilities: Inspect browser accessibility snapshots, screenshots, text, and elements, Click, type, scroll, hover, select, and handle dialogs, Navigate and manage Chrome tabs, Inspect console and network activity, Evaluate JavaScript in the connected browser

Connected profiles

Browser automationindustries

Additional details

Registry identifier

io.github.ofershap/real-browser

Source ↗ · Checked 2026-09-17
Published version

1.2.1

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

real-browser-mcp

Source ↗ · Checked 2026-09-19
Source manifest version

1.3.0

Source ↗ · Checked 2026-09-19
Unattended configuration

The MCP client launches the local npm server; after the separately documented Chrome extension and user session are prepared, the bridge maintains localhost WebSocket reconnect and health checks.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

The integration inherits whatever cookies, sessions, or manually completed SSO exist in the user's Chrome profile; the publisher does not define one MCP authentication scheme, so authentication is unknown and setup requires user authorization.

Source ↗ · Checked 2026-09-19
Connection configuration

The MCP client invokes real-browser-mcp with npx, while the required Chrome extension connects to the server on localhost WebSocket port 7225 by default.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19