QA Touch MCP Serverofficial
A
licenseNot graded
qualityB
maintenanceOfficial MCP server for QA Touch, enabling AI assistants to manage test cases, defects, test runs, and more via natural language.
108 npm
MIT
Qase MCP Server
Officialby qase-tms
Related Servers
Alternatives to Qase MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityFmaintenanceA TypeScript-based MCP server that provides integration with the Qase test management platform, allowing you to manage projects, test cases, runs, results, plans, suites, and shared steps.2612MIT
Nhost MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceOfficial MCP server for the Nhost backend platform. Manage Postgres data, GraphQL, auth, storage, migrations and Hasura metadata via AI assistants.5MIT- AlicenseAqualityBmaintenanceOfficial MCP server for creating and managing AI UGC video ads. Browse assets, estimate credit costs, generate videos, and retrieve completed outputs through eleven typed tools.1131 npmMIT
- AlicenseAqualityCmaintenanceMCP server that integrates with Testmo to let AI assistants read projects, runs, results, and test cases, and create or update runs, results, and cases via natural language.1586 npmMIT
- AlicenseAqualityCmaintenanceMCP server for QTM4J (QMetry Test Management for Jira) Open API, enabling test case and cycle management via natural language.2132 npmMIT
TDQS
A4.4/5.0
Scored across 17 tools
Disambiguation5/5
Each tool targets a distinct action/resource: single vs bulk case writes, CI vs staged run recording, get-by-ID vs QQL search, and general vs triage defects are all clearly separated. The only intentionally overlapping tool is qase_api, but its description explicitly defers to dedicated tools.
Naming Consistency4/5
Most tools follow a qase_<resource>_<action> pattern (qase_case_upsert, qase_run_complete, qase_suite_upsert), and the qql_ prefix cleanly groups the search-language tools. A few names (qase_get, qase_api, qase_discover_tools, qase_triage_defect) deviate from the resource-first pattern, but the convention is still predictable.
Tool Count3/5
At 17 tools the server is at the low end of the heavy range (16-25), though each tool has a clear role and several are deliberate compound/escape-hatch tools. It is a reasonable count for Qase's broad domain, but more than a tightly curated 3-15 tool set.
Completeness4/5
Core workflows are well covered: project context, suites, cases, runs, results, defects, attachments, and general read/search. Delete, plan/milestone, review, and custom-field operations are hidden behind qase_discover_tools rather than present in the visible set, and qase_api covers edge cases, so gaps are minor and workaroundable.
Maintenance
ActivityActive
ResponsivenessSlow