mcp-snapshot-filter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| filter-level | No | Filter level: off, light, moderate, aggressive | moderate |
| upstream-command | Yes | The upstream command to proxy, e.g., 'npx -y chrome-devtools-mcp@latest' |
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 |
|---|---|
| clickC | Clicks on the provided element |
| close_pageA | Closes the page by its index. The last open page cannot be closed. |
| dragB | Drag an element onto another element |
| emulateB | Emulates various features on the target page. |
| evaluate_scriptB | Evaluate a JavaScript function inside the target page. Returns the response as JSON, so returned values have to be JSON-serializable. |
| fillB | Type text into an input, text area or select an option from a element. |
| fill_formA | Fill out multiple form elements (inputs, selects, checkboxes, radios) at once. ALWAYS prefer this tool over multiple individual 'fill' or 'click' calls when interacting with forms. It is significantly faster, more reliable, and reduces turn count. Example: Fill username, password, and check "Remember Me" in one call. |
| get_console_messageA | Gets a console message by its ID. You can get all messages by calling list_console_messages. |
| get_network_requestA | Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel. Useful for inspecting request headers (including 'Cookie') and response headers (including 'Set-Cookie' and directives). |
| handle_dialogA | If a browser dialog was opened, use this command to handle it |
| hoverB | Hover over the provided element |
| lighthouse_auditA | Get Lighthouse score and reports for accessibility, SEO, best practices, and agentic browsing. This excludes performance. For performance audits, run performance_start_trace |
| list_console_messagesA | List all console messages for the target page since the last navigation. |
| list_network_requestsA | Lists the most recent requests for the target page since the last navigation. |
| list_pagesA | Get a list of pages open in the browser. |
| navigate_pageB | Go to a URL, or back, forward, or reload. Use project URL if not specified otherwise. |
| new_pageC | Open a new tab and load a URL. Use project URL if not specified otherwise. |
| performance_analyze_insightA | Provides more detailed information on a specific Performance Insight of an insight set that was highlighted in the results of a trace recording. |
| performance_start_traceA | Start a performance trace on the target webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load speed. |
| performance_stop_traceB | Stop the active performance trace recording on the target webpage. |
| press_keyA | Press a key or key combination. Use this when other input methods like fill() cannot be used (e.g., keyboard shortcuts, navigation keys, or special key combinations). |
| resize_pageB | Resizes the page's window so that the page has specified dimension |
| select_pageA | Select a page as a context for future tool calls. |
| take_heapsnapshotA | Capture a heap snapshot of the target page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks. |
| take_screenshotC | Take a screenshot of the page or element. |
| take_snapshotA | Take a text snapshot of the target page based on the a11y tree. The snapshot lists page elements along with a unique identifier (uid). Always use the latest snapshot. Prefer taking a snapshot over taking a screenshot. The snapshot indicates the element selected in the DevTools Elements panel (if any). |
| type_textA | Type text using keyboard into a previously focused input |
| upload_fileC | Upload a file through a provided element. |
| wait_forB | Wait for the specified text to appear on the selected page. |
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 29 tools
Most tools target a clear, distinct browser action or data source, such as navigation, input, console messages, network requests, or performance tracing. The main ambiguity is between fill, fill_form, and type_text, though the descriptions reduce the risk of misselection.
Most names follow a readable snake_case verb_noun pattern like list_pages, navigate_page, and take_snapshot. However, bare verbs such as click, fill, hover, and drag, plus deviations like lighthouse_audit, new_page, and wait_for, break the otherwise consistent style.
At 29 tools, the surface is too large for a tightly scoped server and crosses the 25+ threshold. Several specialized debugging capabilities like heap snapshots, Lighthouse audits, and performance tracing could be separated into their own servers or grouped more compactly.
The tool set covers the full browser workflow well: page lifecycle, navigation, interaction, forms, dialogs, console and network inspection, screenshots, accessibility audits, performance tracing, and memory analysis. Minor gaps like direct cookie/storage manipulation or an explicit scroll helper can be worked around with evaluate_script or emulate.