Skip to main content
Glama
hooplus1ce

qa-automation-mcp-plugin

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to qa-automation-mcp-plugin

No user-submitted related servers found.

    Related Servers

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, especially the vtable_* family which is subdivided by action (get, scan, scroll, select, drag). A few pairs like vtable_analyze_headers and vtable_scan_columns overlap in analyzing headers, but descriptions clarify their different outputs. Overall, agents can tell tools apart with careful reading.

    Naming Consistency4/5

    Tools generally follow a verb_noun pattern in snake_case (e.g., click_interact, fill_input, capture_screenshot). The vtable_* prefix creates a consistent subsystem, though 'mimo_describe_image' breaks the pattern by leading with a noun and 'execute_and_record' uses a conjunction while 'execute_action_chain' uses a modifier. Still, the overall pattern is predictable.

    Tool Count3/5

    With 24 tools, this is on the heavy side, but the breadth reflects the complexity of QA automation including full VTable support. Each tool serves a distinct function, and the count is justified by the domain, though it demands careful selection.

    Completeness4/5

    The server covers the full recording lifecycle (start, execute, export), generic interaction (click, fill, chain, wait), page analysis, and a deep VTable toolkit. Minor gaps include no dedicated hover, keyboard shortcut, or element state assertion, but these are workarounds via execute_action_chain and wait_for_condition.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources