Browser MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Browser MCPopen example.com and take a screenshot"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sedna Browser MCP
A standalone visual-first browser MCP: look at a live page, act on it, receive the resulting screenshot, and continue in the same browser. A Rust/RMCP host supervises the existing Node/Playwright runtime. Both local stdio and authenticated Streamable HTTP/HTTPS use that same worker implementation.
HTTP candidate status: implementation and tests are present, but this revision has not been compiled or tested over HTTP in its authoring environment. The container has no Rust toolchain/package access. Only the recorded JavaScript/schema checks passed here. See current validation. No GitHub repository or PR has been created by this archive.
Get started
Requires Node.js 22+, Rust (the repository pins 1.99.0), a native C toolchain and Chromium system libraries.
npm ci
npm run setup
node scripts/start.mjs --checkThe pending HTTP lockfile is regenerated explicitly during setup. The final
release build then uses --locked. Install Linux browser system libraries
with npx playwright install --with-deps chromium when necessary.
Stdio remains the default:
node scripts/start.mjsFor an authenticated HTTP service, copy and configure an example outside the repository, then run:
node scripts/start.mjs --transport http --http-config /etc/browser-mcp/http.jsonSee HTTP/HTTPS setup and ownership, proxy example, native TLS example, and Codex HTTP configuration. HTTP always requires issuer-validated, audience-bound, scoped JWTs. A TLS proxy is not a substitute for authorization inside the server.
Related MCP server: mcp-cdp
Tools
Tool | Purpose |
| Inline current screenshot, geometry and compact controls. |
| Bounded ordered actions (including persistent CSS viewport/scroll changes), cleanup, partial receipts and resulting image. |
| Explicit responsive captures with per-view geometry and restoration receipts. |
| Bounded recent console/network records and sequence cursors. |
| Explicit tab operations and actual Chrome target identities. |
| Lifecycle and last-operation reconciliation; HTTP adds owned create/list/close. |
Over HTTP, call browser_session with action: "create", then pass its
browser_session_id on subsequent calls. Two agents sharing credentials do not
automatically share a browser. Stdio keeps its private implicit worker.
Screenshots are typed MCP image blocks, not filenames or base64 embedded in text.
The existing viewport/action semantics and recovery model are documented in architecture, protocol, and operations. HTTP leases add a transport-independent owner check; they do not replace browser/page/observation identities.
Verify and publish PR #1
node scripts/verify.mjsThis resolves any pending lockfile, formats Rust, compiles/tests both transport
modes, runs real Chromium and native TLS tests, and checks packaging. Failures
stop the run. It writes concrete evidence to docs/verification-run.json.
To create the requested new public repository using an authenticated GitHub CLI:
node scripts/publish-pr1.mjsThe script targets only sednalabs/browser-mcp, refuses to modify an existing
repository, runs verification first, creates a minimal licensed main, then
pushes the implementation branch and opens draft PR #1. It never merges a
PR or force-pushes. It requires gh, git and permission to create organization
repositories. Only the explicit SOURCE_MANIFEST.json inventory is copied.
Licence and security
Apache-2.0. NOTICE preserves Sedna/OpenAI Codex provenance. Read SECURITY.md before exposing a browser service. Browser users can act on the network reachable from their browser host; run it in an appropriately isolated environment. The optional CDP endpoint stays private.
The initial server retains stdio compatibility for MCP 2025-11-25 and targets MCP 2026-07-28 via the maintained RMCP 3.5.1 source. Version support is not a claim that this HTTP candidate has already passed its required integration tests.
This server cannot be deployed
Maintenance
Related MCP Connectors
- TabfleetOAuthcom.tabfleet
Launch, inspect, control, and share isolated cloud browsers for your agents.
Give AI agents a real cloud Chrome: open sessions, navigate, read pages, click, type and screenshot.
181Undetectable cloud browser sessions for AI agents and scrapers. Navigate, extract, click, captcha.
Hosted browser for AI agents: screenshots, post-JS DOM, console, WCAG. No install, no API key.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to control a browser over HTTP MCP to open pages, take screenshots, click coordinates, and record audio/video as WebM.MIT
- AlicenseAqualityAmaintenanceEnables agents to inspect and drive Electron or Chrome/Chromium apps via the Chrome DevTools Protocol, exposing DOM snapshots, console logs, network requests, and gated interactions like clicking, typing, and navigating.6252 npm1MIT
- AlicenseNot gradedqualityBmaintenanceLets coding agents control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis. Provides access to Chrome DevTools capabilities such as tracing, network inspection, screenshots, and console messages through MCP clients.2,950,197 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables agents to inspect localhost web applications through Chrome DevTools Protocol by listing Chrome targets, attaching to a page, capturing and querying network, console, navigation, and WebSocket events, and managing ephemeral sessions.81MIT