SmartBear MCP server
OfficialRelated Servers
Alternatives to SmartBear MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with seamless access to SmartBear's suite of testing and monitoring tools, enabling querying testing data, analyzing performance metrics, and managing test automation through natural language.4,262 npmMIT
- AlicenseBqualityCmaintenanceLets AI assistants inspect test run results, AI QA reports, and findings with their full evidence, and, when asked, start runs, re-run only failed tests, import API specs, or scan a website. Read-only tools are free, while work-starting tools consume the workspace's allowance and report usage limits.19MIT

Sauce Labs MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to interact with Sauce Labs testing platform through natural language, providing access to device cloud management, test job analysis, build monitoring, and testing infrastructure insights. Supports both Virtual Device Cloud (VDC) and Real Device Cloud (RDC) with comprehensive test analytics and team collaboration features.3410Apache 2.0- AlicenseAqualityDmaintenanceEnables AI agents to manage Autotest AI projects, screens, test cases, and test runs through natural language commands.10MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with TestRail test management systems through comprehensive API integration. Supports retrieving and updating test cases, projects, suites, runs, and results, plus adding attachments and managing test data through natural language commands.1815 npmMIT
- AlicenseBqualityFmaintenanceEnables AI assistants to interact with Xray Test Management for both Cloud and Server deployments. Supports test execution, importing results from multiple formats (JUnit, Cucumber, Robot Framework, TestNG), and managing test plans and executions.83MIT
TDQS
Scored across 309 tools
Tools are separated by product prefix (e.g., reflect_, swagger_, qmetry_), making cross-product distinctions clear. However, within each product there are many similar fetch/create/update tools (e.g., qmetry_fetch_test_cases vs. qmetry_fetch_test_case_details vs. qmetry_fetch_test_case_steps), which can be confusing in a set of 309 tools.
Names consistently follow a product-prefix + verb_noun pattern (e.g., reflect_list_tests, swagger_create_portal, contract-testing_create_webhook). Minor variations like verb_verb_noun (swagger_create_or_update_api) are rare and still readable.
309 tools is an extreme mismatch for a single MCP server, far exceeding the typical 3-15 range. Even for a multi-product server, this volume likely overwhelms an agent's context and increases misselection risk.
The surface is very broad, covering create/read/update for many entities across products. Some gaps exist (e.g., no delete for QMetry test cases or requirements, no delete portal in Swagger), but most core workflows are supported.