F
licenseNot graded
qualityC
maintenanceEnables MCP-compatible clients to execute Playwright-based UI and API test suites (login, inventory, checkout, API, regression) and receive structured JSON test results.
2 npm
-
MCP DevOps Test Server
by mrchris2000
Related Servers
Alternatives to MCP DevOps Test Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides self-healing UI/API test automation via Plan-Generate-Run-Heal cycle, exposing MCP tools for test platforms to trigger batches and retrieve reports.-
- AlicenseAqualityDmaintenanceThis is an unofficial, community-built MCP server for qTest Manager. Not affiliated with or endorsed by Tricentis. Browse projects, modules, and test cases Create/delete test design modules Create and manage test execution cycles Add test cases into execution suites917 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to discover API endpoints from OpenAPI/Swagger specs, send HTTP requests, validate responses, and analyze status codes for automated API testing.1-
- AlicenseBqualityBmaintenanceEnables managing TestRail projects, suites, cases, sections, runs, tests, results, plans, milestones, and shared steps directly from MCP-supported AI clients.44MIT
- AlicenseNot gradedqualityBmaintenanceEnables pulling test data, inspecting telemetry channels, running analysis, and writing results back from any MCP client.MIT
TDQS
A3.6/5.0
Scored across 6 tools
Disambiguation4/5
Most tools have clearly distinct purposes: projects, tests, execution, results, logs, and download preparation. The only potential confusion is between get_test_results and get_test_log_results, but their descriptions differentiate comprehensive report data from log archive analysis.
Naming Consistency4/5
Tool names follow a consistent verb_noun pattern (get_, list_, execute_, prepare_) and all use snake_case. Minor inconsistency exists between get_ and list_ for retrieval operations, but this is a common and acceptable variation.
Tool Count5/5
With 6 tools, the server is well-scoped for a DevOps test management workflow: project discovery, test listing, execution, result retrieval, log retrieval, and download preparation. Each tool serves a distinct step without unnecessary redundancy.
Completeness4/5
The tool set covers the core lifecycle of test execution: discover projects, list tests, execute tests, retrieve results, and download logs. Minor gaps exist (e.g., no explicit test detail view, no cancellation mechanism), but agents can accomplish primary workflows without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues