jmeter-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JMETER_BIN | No | Absolute path to the jmeter binary. | |
| JMETER_HOME | No | Absolute path to the Apache JMeter installation directory. | |
| JMETER_ENV_FILE | No | Path to an environment file to load JMeter properties at runtime. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_test_planB | Create a new JMeter test plan with a default thread group |
| list_testsA | List all JMeter test files (.jmx) in a directory |
| read_test_fileA | Read and parse a JMeter test file to show its structure |
| create_test_plan_from_api_sourceC | Create a JMeter test plan from an API source. Supported sourceType values: openapi, endpoint. |
| create_test_plan_from_openapiB | Create a JMeter test plan from an OpenAPI YAML/JSON file. Use this when the user asks for a plan based on an OpenAPI file. |
| add_http_samplerB | Add an HTTP request sampler to an existing test plan |
| add_assertionB | Add an assertion to validate responses |
| add_timerB | Add a timer for think time / delays between requests |
| add_csv_data_configC | Add a CSV Data Set Config for data-driven testing |
| update_thread_groupB | Update thread group settings (threads, ramp-up, loops, duration) |
| delete_elementB | Delete an element from a test plan by name |
| run_testC | Run a JMeter test plan and return results |
| generate_reportB | Generate an HTML report from JMeter test results |
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 13 tools
Most tools have clearly distinct purposes, but the three create_test_plan variants overlap, especially create_test_plan_from_api_source with sourceType=openapi and create_test_plan_from_openapi. The explicit routing hint in the OpenAPI tool description helps, but an agent still faces ambiguity about which creation tool to use.
All tools follow a consistent snake_case verb_noun pattern, such as add_http_sampler, update_thread_group, and generate_report. Even the longer create_test_plan_from_* names stay predictable and readable.
Thirteen tools is within the appropriate range for a JMeter-focused server and covers creation, editing, execution, and reporting. The count is slightly higher than necessary because create_test_plan_from_openapi is largely redundant with create_test_plan_from_api_source.
The server covers the main JMeter workflow: create/read plans, add core elements, run tests, and generate reports. However, updates are limited to thread group settings; samplers, assertions, timers, and config elements can only be deleted and recreated, which is a notable gap for iterative test editing.