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.
81 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- AlicenseAqualityDmaintenanceOfficial 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.1114 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.1518 npmMIT
- AlicenseAqualityCmaintenanceMCP server for QTM4J (QMetry Test Management for Jira) Open API, enabling test case and cycle management via natural language.2138 npmMIT
TDQS
A4.3/5.0
Scored across 42 tools
Disambiguation5/5
Each tool has a clearly delineated purpose, with extensive cross-references in descriptions guiding the agent to the right tool (e.g., upsert vs bulk create, ci_report vs result_record). The presence of discovery/help tools reinforces clarity. No overlapping functionality that would cause misselection.
Naming Consistency4/5
Tool names predominantly follow a qase_<entity>_<action> snake_case pattern, with a few exceptions for special operations (e.g., qase_get, qase_api, qase_discover_tools). The convention is consistent and readable, though not perfectly uniform.
Tool Count4/5
42 tools is on the high side, but justified by the breadth of the Qase platform (cases, runs, defects, reviews, etc.). Each tool addresses a distinct operation or entity, and the set avoids redundant tools by providing upsert rather than separate create/update. Still, the volume may feel heavy.
Completeness5/5
The tool set covers the full CRUD lifecycle for major entities (cases, runs, results, defects, reviews, milestones, etc.), plus bulk operations, search, and a generic API fallback. Known API limitations (e.g., review approval is UI-only) are documented, so no gaps in achievable operations.
Maintenance
ActivityActive
ResponsivenessSlow