Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

Related Servers

Alternatives to TestingBot MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Argus E2E Testing Agent, enabling AI coding assistants to perform browser testing, quality intelligence, CI/CD integration, discovery, time travel debugging, visual AI testing, correlation analytics, and API testing directly from the IDE.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A universal AI-powered testing server built on the Model Context Protocol (MCP). Allows AI agents to inspect, execute, test, monitor, debug, and report on software projects.
      3
      GNU Lesser General Public v2.1 only
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables AI agents to measure live web and responsive UIs — contrast ratios, touch targets, overflow, and theme drift — returning precise, selector-attached findings as text. It also lets a human and agent share the same live mobile and desktop session, with pinned notes and screenshots readable by the agent.
      87 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 73 tools

    Disambiguation3/5

    Most tools target distinct resources or workflows, and descriptions often clarify family-specific tools (Maestro vs App Automate vs visual vs accessibility). However, there is notable overlap among session-start tools (startLiveSession, startDesktopLiveSession, startMobileLiveSession, tb_openBrowser, createCdpSession), tunnel cleanup tools (stopTunnel vs deleteTunnel), and screenshot-related tools. The large surface makes boundary decisions harder even when each description is informative.

    Naming Consistency3/5

    Many tools follow a camelCase verb-noun convention, but the set mixes unprefixed camelCase names, a tb_ snake_case-prefixed browser-control family, and noun-style names like maestroCheatSheet. The tb_ grouping is deliberate and readable, but overall naming is not uniform across the server.

    Tool Count2/5

    At 73 tools, the server is far beyond the typical 3-15 well-scoped range and is heavy even for a broad testing platform. Several tools are convenience wrappers or narrow variants, which adds surface area without proportional independent capability.

    Completeness3/5

    The server covers many TestingBot workflows: sessions, tunnels, storage, tests/builds, Maestro, App Automate, accessibility, visual regression, account, and team. Still, several subdomains lack full lifecycle coverage, such as create/update/delete for accessibility and visual tests, cancelling App Automate runs, and deleting Maestro projects. These are notable gaps but agents can often work around them through the dashboard or existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues