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_statusA | Show native host manifest path 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
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.