JMeter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_jmeter_testB | Execute a JMeter test. Args: test_file: Path to the JMeter test file (.jmx) gui_mode: Whether to run in GUI mode (default: False) |
| execute_jmeter_test_non_guiC | Execute a JMeter test in non-GUI mode. Args: test_file: Path to the JMeter test file (.jmx) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are essentially identical in purpose—both execute JMeter tests—with the only difference being that one explicitly specifies non-GUI mode while the other offers it as an optional parameter. This creates significant ambiguity, as an agent would struggle to choose between them for the same core task, leading to potential misselection.
The tool names follow a consistent verb_noun pattern (execute_jmeter_test and execute_jmeter_test_non_gui), which is clear and predictable. However, the redundancy in naming (both starting with 'execute_jmeter_test') slightly detracts from optimal consistency, though the pattern remains largely intact.
With only two tools, the server feels severely under-scoped for a JMeter domain, which typically involves test creation, management, reporting, and analysis. This minimal set limits functionality and suggests incomplete coverage, making it inappropriate for comprehensive use.
The tool surface is extremely incomplete for a JMeter server, lacking essential operations such as creating, editing, listing, or deleting tests, generating reports, or managing test environments. This gap will likely cause agent failures when attempting broader JMeter-related tasks beyond basic execution.