Remote-browserBRAND COLLECTION / ARTICLES
Chrome DevTools MCP
Articles & research.
Connect Chrome DevTools MCP to an existing browser for inspection and debugging. Check endpoint type, authentication, and remote artifact handling.
1–8 of 8 articles
Browser MCP Cursor: Wiring Cursor to a Real Browser
Browser MCP Cursor setups connect the Cursor IDE to a real Chromium session. Here is how the pieces fit, what breaks, and how to run it in production.
Read articleChrome MCP: Wiring AI Agents to a Real Browser
Chrome MCP connects AI agents to a real browser. Learn how the protocol works, where it breaks, and how to run it on hosted Chromium.
Read articleBrowser Control for AI Agents: CDP, MCP, and Hosted Chromium
Browser control for AI agents explained: how CDP, MCP, and Playwright drive real Chromium, where local setups break, and how to run it in production.
Read articleBrowser MCP Chrome Extension: What It Is and What to Use
A browser MCP Chrome extension lets agents drive your local tab. Here's how it works, where it breaks in production, and the hosted Chromium path.
Read articleBenchmark local and remote CDP latency
Run a timing script that records attachment, navigation, failures, and environment metadata.
Read articleBrowser agent vs browser infrastructure
Separate the decision loop, harness, connection protocol, and browser runtime.
Read articleWhat is remote CDP?
Learn where CDP fits between your automation client and a network-accessible Chromium browser.
Read articleBrowser session isolation
Distinguish browser contexts from process, storage, and network isolation.
Read article