Debug Web 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 |
|---|---|
| browser_list_targetsB | List localhost development tabs exposed by a loopback Chrome CDP endpoint. |
| browser_open_sessionB | Attach to one selected localhost development tab. Optionally authorize exact additional localhost origins, such as a separate API port. Chrome and tabs remain user-owned. |
| browser_start_captureB | Capture network, console, navigation, and WebSocket events. Request and response bodies default off; when requested, text/JSON bodies are size-bounded and held only in memory. |
| browser_stop_captureB | Stop capture and return a summary of temporary event data. |
| browser_list_network_requestsC | Query captured network metadata in memory; does not call Chrome. |
| browser_get_network_requestA | Read one captured request with redacted headers and opted-in bodies from memory; does not call Chrome. |
| browser_get_eventsB | Query captured console, navigation, network, and WebSocket events in memory; does not call Chrome. |
| browser_close_sessionA | Detach, close only Debug Web's socket, and discard temporary data; leaves Chrome and the tab open. |
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 8 tools
Each tool has a distinct purpose, but browser_list_network_requests and browser_get_events both query captured network data, causing minor overlap. Descriptions help clarify that one is network-focused metadata and the other is all event types.
All tools follow a consistent browser_verb_noun pattern using snake_case. Names are predictable and readable throughout.
Eight tools are well-scoped for a browser debugging server, covering session and capture lifecycles without excess. Each tool earns its place.
Session lifecycle (list, open, close) and capture lifecycle (start, stop, query) are fully covered. Missing operations like page evaluation or DOM inspection are minor gaps for a capture-focused debugging tool.