Codex Control Chrome MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chrome_statusB | Show native host manifest paths and discovered bridge sockets. |
| chrome_bridge_statusB | Ask the active Codex Control Chrome MCP bridge for status. |
| chrome_get_infoB | Get connected Codex Chrome extension backend info. |
| chrome_name_sessionC | Set the Chrome tab group/session name. |
| chrome_user_tabsA | List user Chrome tabs visible to the extension. |
| chrome_session_tabsA | List tabs currently claimed by this MCP browser session. |
| chrome_create_tabA | Create a new background tab and claim it for this MCP session. |
| chrome_claim_tabC | Claim an existing Chrome tab by numeric tab id. |
| chrome_attach_tabC | Attach Chrome debugger to a claimed tab. |
| chrome_detach_tabC | Detach Chrome debugger from a claimed tab. |
| chrome_cdp_sendC | Send a raw CDP command to a claimed and attached tab. |
| chrome_navigateC | Navigate a claimed tab to a URL using CDP Page.navigate. |
| chrome_evaluateC | Evaluate JavaScript in a claimed tab using Runtime.evaluate. |
| chrome_screenshotC | Capture a screenshot from a claimed tab. Returns base64 PNG. |
| chrome_read_eventsB | Read and clear CDP/download notifications buffered by this MCP process. |
| chrome_finalize_tabsC | Finalize claimed tabs. Use status handoff or deliverable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
The status/info trio (chrome_status, chrome_bridge_status, chrome_get_info) overlaps heavily — all report diagnostic state, and the distinction between 'native host manifest paths', 'bridge status', and 'extension backend info' is subtle enough that an agent may pick the wrong one. The tab tools (user_tabs vs session_tabs, create vs claim vs attach) are reasonably distinct once the descriptions are read.
All names use a consistent chrome_ prefix and snake_case, and most follow verb_noun (chrome_create_tab, chrome_claim_tab, chrome_navigate). Minor deviations: noun-only names (chrome_status, chrome_bridge_status) and one verb-last (chrome_cdp_send).
16 tools is slightly heavy but justified by the layered surface: host/bridge diagnostics, session and tab lifecycle, debugger attach/detach, CDP escape hatch, and high-level navigate/evaluate/screenshot helpers. Each tool maps to a real step in the workflow.
The lifecycle is well covered: discover, name session, create/claim tabs, attach/detach debugger, drive via CDP, evaluate, screenshot, read events, and finalize. Minor gaps: no explicit tab close/release tool, no wait-for-load or focus/activate operation, and no dedicated input (click/type) helper beyond raw chrome_cdp_send.