argus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARGUS_NO_LAUNCH | No | Set to 1 to force-skip Chrome launch regardless of config file. |
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 |
|---|---|
| browser_launchA | Launch a new Chrome browser instance with remote debugging enabled. |
| browser_connectA | Connect to an already-running Chrome instance via WebSocket debugger URL. |
| browser_disconnectA | Disconnect from Chrome (leaves browser running). |
| browser_statusA | Get the current connection status of the browser. |
| tab_listA | List all open browser tabs. |
| tab_openA | Open a new browser tab and navigate to a URL. |
| tab_navigateB | Navigate a tab to a URL. |
| tab_closeA | Close a browser tab. |
| tab_screenshotB | Take a screenshot of a tab. |
| console_startC | Start recording console logs for a tab. |
| console_stopA | Stop recording console logs for a tab. |
| console_get_logsC | Get recorded console logs for a tab. |
| console_clearA | Clear recorded console logs for a tab. |
| network_start_recordingC | Start recording network requests for a tab. |
| network_stop_recordingA | Stop recording network requests for a tab. |
| network_get_requestsB | Get recorded network requests for a tab. |
| network_clear_requestsB | Clear recorded network requests for a tab. |
| network_add_mockC | Add a network mock rule that intercepts matching requests. |
| network_remove_mockB | Remove a network mock rule by ID. |
| network_list_mocksA | List all active network mock rules for a tab. |
| network_clear_mocksB | Remove all network mock rules for a tab. |
| page_evaluateC | Evaluate JavaScript expression in a tab. |
| page_reloadB | Reload a tab. |
| page_get_urlC | Get the current URL of a tab. |
| banner_get_screenshotsA | Retrieve screenshots captured via the Argus banner Screenshot button. Clears the queue after returning. |
| banner_updateB | Push state updates to the Argus banner on a tab (recording indicator, counts). |
| dom_queryB | Query the first element matching a CSS selector and return its properties. |
| dom_query_allA | Query all elements matching a CSS selector and return their properties. |
| dom_clickA | Click the first element matching a CSS selector (scrolls into view first). |
| dom_input_valueA | Set the value of an input element and dispatch input/change events (works with React/Vue controlled inputs). |
| dom_get_valueB | Get the current value of an input element. |
| dom_wait_forC | Wait for an element to appear in the DOM (polls every 100ms). |
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 32 tools
Each tool is namespaced by subsystem (browser, tab, page, dom, network, console, banner) and performs a clearly distinct action. Even similar tools like network_remove_mock versus network_clear_mocks are easily differentiated by specificity.
The naming is largely consistent with a domain_prefix plus action pattern, and all tools use snake_case. Minor deviations like browser_status, tab_screenshot, and dom_input_value break the strict verb_noun pattern but do not cause real confusion.
With 32 tools, the server exceeds the 25-tool threshold and feels heavy even though the tools are organized by subsystem. The count is defensible for a full browser automation surface, but it is still more than a typical MCP server should expose.
The toolset covers core browser automation workflows: browser lifecycle, tabs, DOM interaction, network interception, console logging, and screenshots. However, browser_launch has no corresponding browser_close or quit tool, so a launched Chrome instance cannot be cleanly terminated through the server.