squish-mcp
OfficialRelated Servers
Alternatives to squish-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables AI agents to manage Autotest AI projects, screens, test cases, and test runs through natural language commands.10-
- AlicenseAqualityDmaintenanceEnables AI agents to interact with HP ALM / Quality Center for QA workflows including test case management, test execution, defect tracking, and requirements management.342MIT
- 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.9,082 npmMIT
- FlicenseAqualityCmaintenanceEnables agents to work with Robot Framework by discovering tests and resources, drafting tests from requirements, dry-running and executing suites, and parsing output.xml results.6-
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with the QA Touch test management API, including browsing projects, managing test cases, running tests, recording results, and filing defects.328 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to run, monitor, and manage Cypress tests with features like test discovery, screenshot handling, and multi-browser support.81MIT
TDQS
Scored across 19 tools
Most tools have distinct purposes, but there is some overlap among analysis tools (e.g., analyze_bdd_context vs analyze_bdd_documentation, analyze_existing_patterns vs analyze_global_scripts). Descriptions are detailed enough to differentiate, but an agent might occasionally misinterpret which analysis tool to use.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_bdd_context, create_test_case, generate_bdd_template). There are no deviations or mixed conventions, making the naming predictable.
With 19 tools covering analysis, creation, running, and configuration, the set is well-scoped for a Squish testing server. Each tool serves a clear role without being excessive or insufficient.
The tool surface covers core workflows: creating suites/test cases, analyzing patterns, generating templates, running tests, and managing global scripts. Minor gaps exist, such as missing update/delete operations for test cases or suites, but agents can work around them.