JMeter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JMETER_BIN | Yes | Path to the JMeter executable (e.g., ${JMETER_HOME}/bin/jmeter) | |
| JMETER_HOME | Yes | Path to the JMeter installation directory (e.g., /path/to/apache-jmeter-5.6.3) | |
| JMETER_JAVA_OPTS | No | Optional Java options for JMeter (e.g., -Xms1g -Xmx2g) |
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) properties: Dictionary of JMeter properties to pass with -J (default: None) |
| execute_jmeter_test_non_guiB | Execute a JMeter test in non-GUI mode - supports JMeter properties. Args: test_file: Path to the JMeter test file (.jmx) properties: Dictionary of JMeter properties to pass with -J (default: None) generate_report: Whether to generate report dashboard after load test (default: False) report_output_dir: Output folder for report dashboard (default: None) log_file: Name of JTL file to log sample results to (default: None) |
| analyze_jmeter_resultsC | Analyze JMeter test results and provide a summary of key metrics and insights. Args: jtl_file: Path to the JTL file containing test results detailed: Whether to include detailed analysis (default: False) Returns: str: Analysis results in a formatted string |
| identify_performance_bottlenecksB | Identify performance bottlenecks in JMeter test results. Args: jtl_file: Path to the JTL file containing test results Returns: str: Bottleneck analysis results in a formatted string |
| get_performance_insightsC | Get insights and recommendations for improving performance based on JMeter test results. Args: jtl_file: Path to the JTL file containing test results Returns: str: Performance insights and recommendations in a formatted string |
| generate_visualizationC | Generate visualizations of JMeter test results. Args: jtl_file: Path to the JTL file containing test results visualization_type: Type of visualization to generate (time_series, distribution, comparison, html_report) output_file: Path to save the visualization Returns: str: Path to the generated visualization file |
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 6 tools
Most tools have distinct purposes, but there is some overlap between analyze_jmeter_results, get_performance_insights, and identify_performance_bottlenecks, as all three analyze JTL files and provide insights. However, their descriptions differentiate them enough to avoid major confusion.
All tool names follow a consistent snake_case pattern with clear verb_noun structure, such as analyze_jmeter_results and execute_jmeter_test. The naming is uniform and predictable throughout the set.
With 6 tools, the count is well-scoped for a JMeter server, covering key operations like test execution, result analysis, and visualization. Each tool serves a clear purpose without redundancy.
The toolset covers core JMeter workflows including test execution, result analysis, and visualization, but lacks tools for test creation or modification. This minor gap does not severely hinder typical agent tasks.