TestingBot MCP Server
OfficialRelated Servers
Alternatives to TestingBot MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP 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.-
- AlicenseNot gradedqualityDmaintenanceA 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.3GNU Lesser General Public v2.1 only
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to automate browser testing via Chromium, providing tools for navigation, interaction, and inspection.-
- FlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents to programmatically run tests, query results, and receive intelligent recommendations about test execution strategy.-
- AlicenseNot gradedqualityBmaintenanceMCP serverr for Lastest to manage your tests, AI create them, run them, and speed up AI-development.22Functional Source , Version 1.1, ALv2 Future
- AlicenseNot gradedqualityAmaintenanceThis 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 npmMIT
TDQS
Scored across 73 tools
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.
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.
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.
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.