visual-ui-debug-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Debug mode, e.g., 'vuda:*' | |
| PLAYWRIGHT_SLOW_MO | No | Slow down Playwright operations by the specified amount of milliseconds | |
| PLAYWRIGHT_HEADLESS | No | Set browser headless mode | true |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| enhanced_page_analyzerC | Analyze a page with screenshots, console logs, interactive element mapping, and performance metrics |
| api_endpoint_testerB | Test multiple API endpoints and verify responses |
| navigation_flow_validatorC | Test a sequence of user actions across multiple pages |
| screenshot_urlC | Take a screenshot of a URL |
| dom_inspectorC | Inspect DOM elements and their properties |
| batch_screenshot_urlsB | Capture screenshots of multiple URLs in a grid layout for easy comparison |
| console_monitorC | Monitor console logs on a page |
| performance_analysisC | Analyze page performance metrics |
| visual_comparisonB | Compare two URLs visually and highlight differences |
| batch_screenshot_urlsB | Take screenshots of multiple URLs and display them in a grid |
| screenshot_local_filesB | Take screenshots of local HTML files in a directory |
| playwright_navigateC | Navigate to a URL |
| playwright_clickC | Click an element on the page |
| playwright_iframe_clickA | Click an element in an iframe on the page |
| playwright_fillC | Fill out an input field |
| playwright_selectB | Select an option in a dropdown |
| playwright_hoverB | Hover over an element on the page |
| playwright_evaluateB | Execute JavaScript in the browser console context |
| playwright_console_logsC | Retrieve console logs captured so far |
| playwright_get_visible_textB | Get the visible text content of the current page |
| playwright_get_visible_htmlB | Get the HTML content of the current page |
| playwright_go_backB | Navigate back in browser history |
| playwright_go_forwardA | Navigate forward in browser history |
| playwright_press_keyB | Press a keyboard key (optionally focusing an element first) |
| playwright_dragC | Drag an element to a target location |
| playwright_screenshotC | Take a screenshot of the current page or a specific element |
| ui_workflow_validatorC | Execute and validate a sequence of UI interactions simulating a user workflow. |
| tunnel_helperA | Guide user to expose local ports via Cloudflare tunnel or manage tunnel URLs |
| debug_memoryB | Save and retrieve debugging context including .env variables, selectors, and issues |
| sitemap_crawlerB | Crawl a website recursively to generate a comprehensive sitemap with all endpoints, links, and visible text content. Perfect for detecting inconsistent content, broken links, and navigation issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Browser console logs | |
| Visual Debugging Protocol Guide | Core workflow patterns and best practices for visual UI debugging |
| Comprehensive UI/UX Debugging Prompt | 5-section debugging process for thorough UI/UX testing |
| VUDA Iterative Debug Loop Protocol | Automatic execution loop for systematic debugging with task management |
TDQS
Scored across 29 tools
Many tools overlap in functionality, such as multiple screenshot tools (batch_screenshot_urls, playwright_screenshot, screenshot_local_files, screenshot_url) and analysis tools (enhanced_page_analyzer, performance_analysis, visual_comparison, dom_inspector). The distinction between low-level Playwright commands and high-level compound tools is unclear, causing potential misselection.
Naming conventions vary: some tools use snake_case (api_endpoint_tester), others use 'playwright_' prefix for low-level actions, and some are standalone (visual_comparison, sitemap_crawler). This inconsistency makes it hard to predict tool names.
With 29 tools, the set is overly large for a UI debugging agent. Many tools are redundant or could be merged, such as the various screenshot and analysis tools. A more streamlined set would be more manageable.
The tool set covers basic browser automation, screenshot, DOM inspection, performance, and workflow validation. However, there are gaps like network monitoring, accessibility checks, and event listeners. Some tools (debug_memory) seem peripheral, reducing overall coverage for the stated purpose.