Browser
Let your agent load authenticated web pages through Chrome DevTools Protocol when APIs are missing or behind login.
Overview
cherchyk/browser is a Build-phase MCP server that loads authenticated web pages for agents using Chrome DevTools Protocol over a local stdio connection.
What is this MCP server?
- Loads web pages using Chrome DevTools Protocol (CDP)
- Supports authenticated sessions instead of anonymous fetch-only flows
- stdio npm package mcpbrowser identifier for local MCP wiring
- Version 0.2.1—lighter scope than the full MCPBrowser automation suite
- GitHub source at cherchyk/MCPBrowser monorepo
- Package version 0.2.1
- Transport: stdio via npm identifier mcpbrowser
- Repository: github.com/cherchyk/MCPBrowser
Community signal: 7 GitHub stars.
What problem does it solve?
Your agent cannot reach the data or UI you need because the site requires a real browser login and simple HTTP clients fail.
Who is it for?
Indie builders wiring agents to session-gated web apps during build and early integration testing.
Skip if: Headless scraping at scale without Chrome, or teams that only need the richer JS execution and anti-bot features of MCPBrowser 0.3.x.
What do I get? / Deliverables
Authenticated page content becomes available to the agent through CDP so you can verify flows, extract visible state, or unblock integration prototypes.
- Agent-accessible content from authenticated web pages
- CDP-backed load path for integration and QA scripts
- Foundation for richer browser workflows in the MCPBrowser repo
Recommended MCP Servers
Journey fit
Authenticated page loading is an integration concern—you wire real browser sessions into agent workflows while building features that depend on live web UIs. CDP-backed page fetch sits beside API clients and scrapers as a build-time integration path for data and UI verification.
How it compares
Authenticated CDP page-load MCP—not a SaaS catalog or declarative multi-agent orchestrator.
Common Questions / FAQ
Who is cherchyk/browser MCP for?
It is for developers using AI coding agents who must read authenticated web pages through Chrome DevTools Protocol instead of public APIs.
When should I use cherchyk/browser MCP?
Use it while building or testing integrations against login-protected dashboards, admin consoles, or legacy web UIs without official machine interfaces.
How do I add cherchyk/browser MCP to my agent?
Install the npm package mcpbrowser (0.2.1), configure your MCP client for stdio transport pointing at that server, and ensure Chrome/CDP is available per the GitHub MCPBrowser project docs.