Chrome Ops 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 | Check whether Chrome Ops Host and the Chrome extension are connected. |
| tabs_listA | List Chrome tabs and their ids, URLs, titles and active state. |
| tab_activateB | Activate a Chrome tab by id. |
| devtools_attachB | Attach Chrome DevTools Protocol to a tab and start collecting Console, Log and Network events. |
| devtools_detachB | Detach Chrome DevTools Protocol from a tab. |
| console_readC | Read captured console/log entries for a tab. |
| network_readC | Read captured HTTP/WebSocket/EventSource activity. Cookie, authorization, and cookie-value fields are redacted before leaving Chrome. |
| network_requestsB | List HTTP requests observed since DevTools attach, summarized by request id, URL, method, status and failure state. |
| network_failuresB | List only failed HTTP requests or responses with status >= 400. |
| network_response_bodyB | Get the response body for a captured request id. Use network_requests first to identify the request. |
| websocket_messagesA | Read captured WebSocket lifecycle and frame events for a tab. |
| eventsource_messagesA | Read captured Server-Sent Events (EventSource) messages for a tab. |
| runtime_evaluateB | Evaluate JavaScript in the inspected tab using Chrome DevTools Protocol Runtime.evaluate. |
| page_reloadA | Reload an inspected tab through Chrome DevTools Protocol so subsequent network activity can be captured. |
| extensions_listA | List installed Chrome extensions/apps including enabled and install type. |
| extension_getB | Get metadata for one installed extension, including install type and enabled state. |
| extension_set_enabledA | Enable or disable an installed extension. Chrome may require a user gesture/confirmation. |
| extension_uninstallB | Request uninstall of another extension. Chrome always presents confirmation for another extension. |
| extension_dev_loadB | Load an unpacked Chrome extension directory through the restricted native helper. The directory must contain manifest.json. |
| extension_dev_reloadA | Reload an installed unpacked extension by exact extension id through Chrome's extension-management UI. |
| extension_dev_errorsA | Open the Errors view for an unpacked extension by exact extension id. |
| extension_dev_removeA | Remove an unpacked extension by exact extension id and verify it disappeared from chrome.management. |
| content_setting_getC | Get an effective per-site Chrome content setting. |
| content_setting_setC | Set a per-site Chrome content setting using the extension API. |
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 24 tools
Tools are mostly distinct, with clear separation between status, tabs, DevTools capture, extension management, and content settings. The network family has some overlap, but each tool is scoped specifically enough to avoid serious misselection.
Most tools follow a resource_verb snake_case pattern such as tabs_list, extension_get, and content_setting_set. Minor inconsistencies like chrome_status and extension_dev_errors, plus singular/plural variations, keep this from being a perfect 5.
At 24 tools, the server is at the heavy end and includes very granular network and extension-dev groupings. The broad Chrome Ops scope justifies many tools, but the count feels borderline compared to a tighter, well-scoped server.
The surface covers connection health, tab activation, DevTools monitoring, runtime evaluation, extensions, and content settings. Obvious gaps like tab creation/closing and direct URL navigation are missing, though agents can partially work around them with runtime_evaluate.