Inspect and automate Chrome pages through browser MCP servers and DevTools tooling. For Codex, 2 routes are explicitly documented by the integration maintainer.
The Chrome DevTools MCP server exposes browser inspection, interaction and performance tools.
Platforms: Windows, macOS, Linux
The maintainer documents Codex setup for this connection.
A supported Node.js runtime, Chrome and the documented server or existing-browser connection setup.
Session attachment needs the documented browser configuration. Browser context and server options affect available tools.
Microsoft’s Playwright MCP server automates supported browsers with structured page interaction tools.
Platforms: Windows, macOS, Linux
The maintainer documents Codex setup for this connection.
Node.js and a supported browser or Playwright-managed browser installation; existing Chrome/Edge sessions need the extension route.
Attaching an existing browser through the extension supports Chrome and Edge. Firefox uses the managed-browser route.
| Integration | Codex compatibility | Requirements |
|---|---|---|
| Chrome DevTools MCP | Documented setup Setup guide | A supported Node.js runtime, Chrome and the documented server or existing-browser connection setup. |
| Playwright MCP | Documented setup Setup guide | Node.js and a supported browser or Playwright-managed browser installation; existing Chrome/Edge sessions need the extension route. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Codex and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All Google Chrome integrations