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 binary (e.g., /path/to/apache-jmeter-5.6.3/bin/jmeter). | |
| JMETER_HOME | Yes | Path to the Apache JMeter installation directory (e.g., /path/to/apache-jmeter-5.6.3). | |
| JMETER_JAVA_OPTS | No | Optional JMeter Java options for configuring JVM settings (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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
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: analyzing results, executing tests, generating visualizations, and identifying bottlenecks. However, 'analyze_jmeter_results' and 'get_performance_insights' could be confused as both provide analysis from test results, though one focuses on metrics and the other on recommendations.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as 'execute_jmeter_test' and 'generate_visualization'. The naming is uniform and predictable across all six tools.
With 6 tools, the server is well-scoped for JMeter testing, covering execution, analysis, visualization, and bottleneck identification. Each tool serves a clear purpose without being overly sparse or bloated.
The tool set covers key aspects of JMeter testing: execution (with GUI and non-GUI options), result analysis, visualization, and bottleneck insights. A minor gap is the lack of tools for test creation or editing, but core workflows are well-supported.