Skip to main content
Glama
samihalawa

visual-ui-debug-agent-mcp

by samihalawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to visual-ui-debug-agent-mcp

No user-submitted related servers found.

    Related Servers

    • playwright-trace-decoder-mcp

      vola-trebla
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that unpacks and structures Playwright trace.zip archives so AI agents can perform root-cause analysis on CI failures, with 16 focused tools for inspection, DOM/UI analysis, root-cause analysis, and performance analysis.
      19
      55 npm
      1
      MIT

    • MCP Playwright Server

      MostafaRaafat91
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI-powered browser automation, web scraping, and testing using Playwright across Chromium, Firefox, and WebKit. It allows users to perform actions like navigation, clicking, typing, and taking screenshots through natural language interfaces.
      17 npm
      MIT

    • browser-test-mcp

      l0s3r-Q
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that fuses Playwright and browser-use for browser automation testing, offering 59 tools for AI-driven exploration and precise assertions on a shared browser instance, with built-in stealth anti-detection.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.6/5.0

    Scored across 29 tools

    Disambiguation2/5

    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 Consistency2/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources