k6-loadtest-mcp
Related Servers
Alternatives to k6-loadtest-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables running k6 load tests with customizable duration and virtual users via natural language, with real-time output and LLM-powered analysis.1-
- AlicenseAqualityAmaintenanceEnables LLM agents to run self-healing JMeter performance tests via natural language, from environment setup to capacity discovery and SLO verdict reporting.121MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically create, execute, and analyze Apache JMeter performance tests. It supports automated bottleneck detection, report generation, and distributed testing management through natural language.MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server implementation that allows AI assistants to run k6 load tests through natural language commands, supporting custom test durations and virtual users.226MIT
- FlicenseNot gradedqualityCmaintenanceIntegrates Apache JMeter with AI assistants to run and manage load tests through natural language. It enables users to execute test plans, parse results, inspect test structures, and compare performance metrics across different runs.-
- AlicenseNot gradedqualityCmaintenanceConverts non-functional requirements and code into secure, traceable JMeter performance tests with coverage analysis, plan generation, execution, and GitHub draft PRs.45 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role in the k6 testing pipeline: generate script, smoke test, full load test, parse metrics, and a convenience orchestrator. No two tools overlap in purpose, and the descriptions emphasize their unique inputs and outputs.
All tool names follow a consistent snake_case verb_noun pattern: generate_k6_script, smoke_test_script, run_load_test, get_test_metrics, run_full_test. The verbs clearly indicate actions, and nouns identify the target, making the set predictable.
Five tools is a well-scoped size for a load-testing server. Each tool maps to a necessary step in the workflow, and the convenience wrapper avoids redundancy without bloating the surface.
The core load-testing lifecycle is covered: script generation, smoke testing, full execution, metrics retrieval, and an all-in-one runner. Minor gaps exist around script editing or cleanup, but the provided workflow is complete enough for typical use.