testit-mcp-server
Related Servers
Alternatives to testit-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables managing TestRail projects, suites, cases, sections, runs, tests, results, plans, milestones, and shared steps directly from MCP-supported AI clients.44MIT
- FlicenseAqualityDmaintenanceEnables management of TestMu AI test projects, test cases, test runs, and integration with Jira, HyperExecute, and AI insights through natural language.391-
- AlicenseAqualityCmaintenanceEnables to interact with Jira AIO Test Case Management System, allowing retrieval of test cases, projects, folders, and search functionality.7Apache 2.0
- AlicenseAqualityDmaintenanceEnables interaction with Xray Cloud and Data Center for test management, including authentication, GraphQL queries, test execution/plan management, and result import via MCP.9MIT
- AlicenseBqualityDmaintenanceEnables management of TestRail projects, suites, test cases, runs, and results through natural language.42MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with TestRail test management system, supporting full CRUD operations on projects, suites, sections, test cases, runs, results, plans, and milestones.35327 npm1MIT
TDQS
Scored across 130 tools
Most tools target a distinct resource and action, and descriptions explicitly disambiguate close pairs such as list vs search, set vs update, and the multiple create_test_run_from_* variants. However, the 130-tool surface includes several near-duplicate patterns and lifecycle variants that can still cause misselection under load.
Names consistently use snake_case verb_noun phrasing (list_, get_, create_, set_, delete_, restore_, purge_) across all resources. Minor variants like create_test_plan_clone and rerun_test_run_results remain readable and follow the same convention.
130 tools far exceeds the 3-15 range appropriate for an MCP server and the 25+ threshold for 'too many'; even for a broad test-management API, this volume creates significant selection and context burden.
The surface covers CRUD and lifecycle operations for projects, work items, sections, test plans, suites, runs, results, autotests, configurations, attachments, comments, shared steps, tags, and analytics. Stated API limitations (e.g. no user list, no autotest restore/purge) are documented rather than hidden gaps.