F
licenseC
qualityD
maintenanceA Model Context Protocol server that enables execution of JMeter performance tests through AI assistants and MCP-compatible clients like Claude, Cursor, and Windsurf.
2
-
JMeter MCP Server
Related Servers
Alternatives to JMeter MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that allows AI assistants to execute and manage JMeter performance tests through natural language commands.673-
- AlicenseBqualityCmaintenanceMCP server for generating, validating, running, and reporting Apache JMeter API performance tests from structured API sources.13700 npmMIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.114 npm-
- FlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that can be deployed locally via stdio or remotely via SSE/HTTP endpoints, supporting multiple MCP clients including VS Code, Cursor, Windsurf, and Claude Desktop.1-
- AlicenseNot gradedqualityDmaintenanceA powerful MCP server for automated JMeter test generation and execution with Docker integration and comprehensive performance analysis.700 npm1MIT
TDQS
C2.6/5.0
Scored across 2 tools
Disambiguation1/5
The two tools are essentially identical in purpose—both execute JMeter tests—with only a minor difference in GUI mode handling. The second tool's name and description suggest it's a redundant subset of the first, creating clear ambiguity and making it impossible for an agent to reliably choose between them without guessing.
Naming Consistency4/5
Both tools follow a consistent verb_noun pattern (execute_jmeter_test and execute_jmeter_test_non_gui), which is clear and predictable. The slight deviation in the second tool's name (adding '_non_gui') is logical and maintains readability, though it hints at the redundancy issue rather than a naming inconsistency.
Tool Count2/5
With only two tools, this server feels severely under-scoped for a JMeter testing domain, as it lacks basic operations like listing tests, viewing results, or managing configurations. The redundancy between the tools exacerbates this, making the set appear incomplete and poorly thought-out for practical use.
Completeness2/5
The tool set is highly incomplete for a JMeter server, covering only test execution and missing essential CRUD operations such as creating, updating, or deleting tests, as well as retrieving results or managing test plans. This will likely cause agent failures when trying to perform common testing workflows beyond a single execution.
Maintenance
ActivityInactive
ResponsivenessNo issues