JMeter MCP Server
Provides configuration for JMeter path and Java options through environment variables
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@JMeter MCP Server run the load test at /tests/ecommerce.jmx"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
π JMeter MCP Server
This is a Model Context Protocol (MCP) server that allows executing JMeter tests through MCP-compatible clients.
π’ Looking for an AI Assistant inside JMeter? π Check outFeather Wand

π Features
π Execute JMeter tests in non-GUI mode
π₯οΈ Launch JMeter in GUI mode
π Capture and return execution output
Related MCP server: my-mcp-server
π οΈ Installation
Local Installation
Install
uv:Ensure JMeter is installed on your system and accessible via the command line.
β οΈ Important: Make sure JMeter is executable. You can do this by running:
chmod +x /path/to/jmeter/bin/jmeterConfigure the
.envfile, refer to the.env.examplefile for details.
# JMeter Configuration
JMETER_HOME=/path/to/apache-jmeter-5.6.3
JMETER_BIN=${JMETER_HOME}/bin/jmeter
# Optional: JMeter Java options
JMETER_JAVA_OPTS="-Xms1g -Xmx2g"π» MCP Usage
Connect to the server using an MCP-compatible client (e.g., Claude Desktop, Cursor, Windsurf)
Send a prompt to the server:
Run JMeter test /path/to/test.jmxMCP compatible client will use the available tools:
π₯οΈ
execute_jmeter_test: Launches JMeter in GUI mode, but doesn't execute test as per the JMeter designπ
execute_jmeter_test_non_gui: Execute a JMeter test in non-GUI mode (default mode for better performance)
ποΈ MCP Configuration
Add the following configuration to your MCP client config:
{
"mcpServers": {
"jmeter": {
"command": "/path/to/uv",
"args": [
"--directory",
"/path/to/jmeter-mcp-server",
"run",
"jmeter_server.py"
]
}
}
}β¨ Use case
LLM powered result analysis: Collect and analyze test results.
Debugging: Execute tests in non-GUI mode for debugging.
π Error Handling
The server will:
Validate that the test file exists
Check that the file has a .jmx extension
Capture and return any execution errors
Available Tools
2 toolsexecute_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)
Inputs: test_file (required), gui_mode. Returns: result
execute_jmeter_test_non_guiC
Execute a JMeter test in non-GUI mode.
Args: test_file: Path to the JMeter test file (.jmx)
Inputs: test_file (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 2 tools
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.
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.
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.
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
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yoβ¦
MCP server for building and testing AI agents with multi-model experimentation and insights.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Related MCP Servers
- FlicenseBqualityCmaintenanceA Model Context Protocol server that allows AI assistants to execute and manage JMeter performance tests through natural language commands.674-
- 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.-
- FlicenseCqualityDmaintenanceA Model Context Protocol server that enables execution of JMeter performance tests through AI assistants and MCP-compatible clients like Claude, Cursor, and Windsurf.2-
- 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-