JMeter MCP Server
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 load test on /tests/api-load.jmx with 100 users"
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: JMeter 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 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.
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.
AI-native mock API server with MCP. Create REST/SOAP mocks from Claude, Cursor, or Windsurf.
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.
Related MCP Servers
- AlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server implementation that allows AI assistants to run k6 load tests through natural language commands, supporting custom test durations and virtual users.226MIT
- FlicenseBqualityCmaintenanceA Model Context Protocol server that allows AI assistants to execute and manage JMeter performance tests through natural language commands.674-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that enables API test automation across various AI hosts (Claude, OpenAI, custom) using Postman Collections.MIT
- FlicenseCqualityDmaintenanceA Model Context Protocol server that enables executing and interacting with JMeter tests through MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.2-