Codex Control Chrome MCP
Related Servers
Alternatives to Codex Control Chrome MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceExposes Codex's Chrome plugin as an MCP server, enabling MCP clients to drive a real, logged-in Chrome browser by navigating, snapshotting the DOM, clicking, typing, taking screenshots, running Playwright, and sending raw CDP commands.20-
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.1,010,088 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceLets coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.1,010,088 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables local opencode agents to control a live Chrome browser via MCP tools, including tab management, JavaScript execution, clicking, form filling, page reading, screenshots, and console log retrieval.MIT
- AlicenseNot gradedqualityCmaintenanceExposes the local agent-browser CLI as MCP tools for browser automation and provides one-command integration with Codex. Enables navigation, interaction, page reading, tab management, and session control through natural language commands.5 npmMIT
- AlicenseNot gradedqualityCmaintenanceLets AI coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.15 npmApache 2.0
TDQS
Scored across 16 tools
Each tool has a clearly distinct function (e.g., attach, detach, claim, navigate, evaluate). While chrome_session_tabs and chrome_user_tabs both list tabs, their contexts differ (claimed vs. all user tabs), and descriptions clarify the distinction.
All tools follow a consistent 'chrome_verb_noun' snake_case pattern (e.g., chrome_attach_tab, chrome_create_tab, chrome_evaluate). No mixing of conventions or abbreviations.
With 16 tools, the count is slightly above the typical well-scoped range (3-15), but each tool serves a specific purpose in Chrome tab automation (e.g., claiming, navigating, evaluating, screenshotting), justifying the number.
The tool set covers the full lifecycle of tab control: creation, claiming, attachment, navigation, evaluation, screenshot, and finalization. Minor gaps exist (e.g., explicit 'close tab' tool is missing, but finalize_tabs may handle it), but core workflows are complete.