Repository navigation
Releases: Blazemeter/jmeter-mcp-plugin
Releases · Blazemeter/jmeter-mcp-plugin
Release list
v1.0.0
BlazeMeter MCP Plugin 1.0.0 is the first release. It adds an MCP client to Apache JMeter so the same test plan can check, automate, or load-test a Model Context Protocol server.
Components
- bzm - MCP Client Config shares one MCP client across the test. Transports are STDIO, SSE, and Streamable HTTP.
- bzm - MCP Server Process starts an HTTP or SSE MCP server from the test plan, for example @modelcontextprotocol/server-everything.
- bzm - MCP Sampler calls that client and records each call as a sample.
Sampler operations
PING, LIST_TOOLS, CALL_TOOL, LIST_RESOURCES, READ_RESOURCE, LIST_PROMPTS, and GET_PROMPT.
CALL_TOOL can load the tool argument schema in the GUI. A tool result with isError=true fails the sample.
Also in this release
- HTTP headers come from an HTTP Header Manager on the client config, including Authorization for a hosted MCP server.
- Connect and initialize can run when the test starts, or on the first sampler. Elapsed time is the MCP call only. Time spent waiting for the client is Connect Time.
- Sample results show request headers, MCP session metadata in response headers, and pretty-printed JSON in the body.
- The managed server process stops when the test ends. HTTP clients are closed first so the SSE stream shuts down cleanly.
- STDIO commands resolve on Windows through PATHEXT.
- An MCP v2 server (2026-07-28) fails the sample with a clear “not supported” message.
- Example plans for STDIO, SSE and Streamable HTTP are in examples/.
Requirements
Java 17 or 21 with JMeter through 5.6.3. The shaded JAR bundles the MCP SDK, so Plugins Manager or a copy into JMETER_HOME/lib/ext is enough.