QA Studio MCP Server
Related Servers
Alternatives to QA Studio MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with the QA Touch test management API, including browsing projects, managing test cases, running tests, recording results, and filing defects.32MIT

TestOptim MCP serverofficial
AlicenseNot gradedqualityCmaintenanceConnects MCP clients such as Claude Code, Cursor and VS Code to a hosted QA service so the assistant can start and monitor test runs on a web app, explore its pages and flows, and read the bugs those runs uncover. Access is scoped by API key permissions, letting read-only keys list projects and issues while write-enabled keys trigger or stop runs.MIT- AlicenseNot gradedqualityCmaintenanceEnables integration with Qase test management platform to create, retrieve, and manage test cases, test suites, and test runs through natural language interactions.ISC
- AlicenseBqualityDmaintenanceIntegrates TestRail with Claude Code to enable AI-assisted test management workflows, including project, suite, test case, test run, and result operations.13MIT
- 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
- AlicenseAqualityDmaintenanceEnables AI agents to manage Autotest AI projects, screens, test cases, and test runs through natural language commands.10MIT
TDQS
Scored across 7 tools
Most tools target distinct resources+actions (list-projects, create-test-case, create-test-run). The main risk is get-test-run vs get-test-results, but the descriptions clarify one returns run metadata and the other returns per-result records. Boundaries are otherwise clear.
All tools follow a strict verb_noun kebab-case convention (get-test-run, list-projects, submit-test-results, create-test-case, etc.). No mixing of styles or inconsistent verbs.
Seven tools is well within the healthy range and each maps to a clear operation. It is slightly lean for a full test-management surface, but nothing is redundant or bloated.
Coverage includes reads (list/get for projects, runs, results), creates (test case, test run), and result submission. However, there is no list/get for test cases, no update or delete for test cases or runs, and no way to close/finalize a run, leaving notable lifecycle gaps.