chrome-pilot-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chrome_statusB | Check Chrome connection status |
| chrome_connectA | Connect to an already-running Chrome browser via DevTools Protocol. Chrome must have remote debugging enabled (chrome://inspect/#remote-debugging). |
| chrome_disconnectA | Disconnect from Chrome (does not close the browser) |
| chrome_list_tabsA | List all open tabs with their title and URL |
| chrome_select_tabA | Switch to a tab by index (from chrome_list_tabs) |
| chrome_close_tabB | Close a tab by index |
| chrome_navigateA | Navigate the active tab to a URL |
| chrome_backA | Go back in browser history |
| chrome_forwardB | Go forward in browser history |
| chrome_reloadB | Reload the current page |
| chrome_clickB | Click on an element by CSS selector or coordinates |
| chrome_typeC | Type text into a focused element or a specific element by selector |
| chrome_scrollC | Scroll the page or a specific element |
| chrome_press_keyC | Press a keyboard key |
| chrome_screenshotA | Take a screenshot of the current page (returns base64 image) |
| chrome_dump_domA | Get the DOM HTML of the page or a specific element |
| chrome_evaluateB | Execute JavaScript in the page context and return the result |
| chrome_fill_formB | Fill multiple form fields at once |
| chrome_select_optionA | Select an option from a dropdown |
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 19 tools
Each tool has a clear, dedicated purpose: lifecycle (connect/disconnect/status), tab management (list/select/close), navigation (navigate/back/forward/reload), interaction (click/type/scroll/press_key), page inspection (screenshot/dump_dom/evaluate), and form helpers (fill_form/select_option). No two tools target the same action; even type and fill_form are distinguished by single vs. multi-field.
All tools are lowercase snake_case with a uniform chrome_ prefix. The second part nearly always follows a verb or verb_noun pattern (e.g., list_tabs, select_tab, click, navigate). This makes the tool set predictable and easy to navigate.
At 19 tools, the server is on the heavier side. While each tool is justifiable, several shortcuts (fill_form, select_option) could be composed from more primitive tools, and the count feels more like a comprehensive library than a minimal set. This is borderline appropriate for a browser automation tool.
Core browser operations are covered: tab lifecycle, navigation, input, screenshots, DOM access, and JS evaluation. However, there is no direct way to create a new tab or wait for conditions, which falls short of full browser automation coverage. These gaps are workable via evaluate, so minor.