web-scout
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEADLESS | No | 无头模式（"true" 不显示浏览器窗口） | false |
| BROWSER_PATH | No | 浏览器路径，"edge" 使用 Edge | |
| LOGIN_TIMEOUT | No | 登录最大等待秒数 | 300 |
| USER_DATA_DIR | No | 持久化用户文件夹，保留登录态 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scout_openA | Open / manage the browser session. Finds or launches a Chromium on port 9222. Clears old tabs and resets the API pool. Does NOT navigate — use scout_goto() for that. Returns: Browser session status. |
| scout_gotoA | Navigate to a URL and capture API requests. Starts network monitoring BEFORE navigating (required: listen.start() must precede any action that triggers requests). Returns page text and interactive elements. Use new_tab=True to open in a new tab while keeping the current page. |
| scout_closeA | Close the browser and clear all captured data. Kills the Chromium process on port 9222 and resets all state. Returns: Status message. |
| scout_tabsA | List all open browser tabs with CDP short IDs. Returns: Tab list with short IDs and current marker. |
| scout_tab_switchA | Switch the active tab by CDP short ID (from scout_tabs output). After switching, scout_goto() targets the new tab. |
| scout_tab_closeA | Close browser tab(s) by CDP short ID and prune their API records. Supports comma-separated IDs for batch close (e.g. "C724404D,5FD84E84"). Empty = close current tab. |
| scout_fetchA | Fetch full page content — scrolls to bottom, dumps innerText + AXTree links, writes to cache file, returns chunked segments. First call scrolls to bottom and writes a JSON cache file. Subsequent calls with start_index read from cache (no re-scroll). |
| scout_screenshotC | Take a screenshot of the current page. |
| scout_elementsB | List interactive page elements, repeated DOM containers, and common actions. Scans for clickable buttons, links, inputs and detects repeated container structures (card layouts, list items, etc.). Returns: Numbered list of interactive elements + DOM containers + Common Actions. |
| scout_cookiesC | View cookies for the current page. |
| scout_actA | Execute actions on the page: input, scroll, click, or select. Two modes:
Each step reports new API method + path inline so AI sees them immediately. |
| scout_loginA | Wait for the user to manually log in via the browser window. Detects login by polling cookies: if cookie names change or ≥2 values change simultaneously, login is detected. Works across all sites without site-specific logic. |
| scout_apisA | List all captured API endpoints, optionally filtered by keyword. |
| scout_inspectC | Show full request and response details for one or more APIs. |
| scout_searchA | Search for data by keyword across ALL captured network data. Supports comma-separated keywords for OR search. |
| scout_contextC | Search all data sources for keyword, returning field paths and values. |
| scout_exportC | Export one or more captured API data sources. |
| scout_export_allB | Export all captured API data sources at once. |
| scout_peekC | One-shot API discovery: open a URL, capture and inspect matching API. |
| scout_requestA | Send a test HTTP request — replay from captured API or fully custom. Two modes:
Cookies are auto-synced from the current browser tab. |
| scout_scanA | Comprehensive page data source scanner with two modes. MODE "all" — full page scan (default):
MODE "dom" — keyword-targeted DOM scan: Searches DOM for containers matching the keyword. |
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 21 tools
Most tools have distinct purposes, but there is some overlap between scout_scan, scout_search, and scout_context, which all involve searching different data sources. Descriptions help differentiate but could still confuse an agent.
All tools share the 'scout_' prefix, but the naming pattern mixes verbs (e.g., scout_act, scout_fetch) and nouns (e.g., scout_apis, scout_cookies). This inconsistency, while readable, could be more uniform.
21 tools is slightly above the typical well-scoped range (3-15), but the domain of browser automation and API discovery justifies many of them. The count feels reasonable, not excessive.
The tool set covers navigation, interaction, API capture, data export, tab management, and login. Minor gaps like cookie management or local storage access exist, but core workflows are well-supported.