No user-submitted related servers found.
Scored across 308 tools
Product prefixes provide some orientation, but multiple toolsets overlap heavily on the same domain: qtm4j_, qmetry_, zephyr_, reflect_, and bearq_ all manage test cases, cycles, and executions, so an agent cannot tell which product to use from the name alone. Within contract-testing, the ten get_bdct_* variants differ only subtly, and tools like contract-testing_test_execute_webhooks vs contract-testing_execute_webhook are near-duplicates.
The same operations are named differently across the server (list_ vs fetch_ vs get_ vs search_, create vs add, update vs edit/patch), and prefixes mix hyphens (contract-testing_) with underscores (qmetry_). Some names are awkward or inconsistent, such as contract-testing_get_bdct_x-contract_test_results_by_consumer and bearq_run_tests_in_functional_areas, though nearly everything is at least snake_case.
308 tools is an extreme count that will overwhelm any agent's selection process and context. Even for a multi-product QA suite, bundling this many operations into one MCP server is far beyond a coherent, manageable scope (typical well-scoped servers are 3-15 tools).
The aggregate covers many workflows, but individual products have notable gaps: Zephyr has no delete for test cases/cycles, Reflect has no update/delete for tests or segments, BearQ has no create/update except via a chat escape hatch, and QTM4J/QMetry lack delete operations for core entities. The overlapping duplicate surfaces also make gaps harder to detect, so agents will hit dead ends in several sub-domains.