BlazeMeter MCP Server
The BlazeMeter MCP Server connects AI tools directly to BlazeMeter's cloud-based performance testing platform. This gives AI agents, assistants, and chatbots the ability to manage complete load testing workflows from creation to execution and reporting. All through natural language interactions.
Prerequisites
- BlazeMeter API credentials (API Key ID and Secret)
- Comply Blazemeter AI Consent
- Compatible MCP host (VS Code, Claude Desktop, Cursor, Windsurf, etc.)
- Docker (only for Docker-based deployment)
- uv and Python 3.11+ (only for installation from source code distribution)
Setup
Get BlazeMeter API Credentials
Follow the BlazeMeter API Keys guide to obtain your API keys as JSON.
Quick Setup with CLI Tool ⚡
The easiest way to configure your MCP client is using our interactive CLI tool:
- Download the appropriate binary for your operating system from the Releases page
- Place the binary in the same folder as your
api-keys.jsonfile - Execute or Double-click the binary to launch the interactive configuration tool
- The tool automatically generates the JSON configuration file for you
Manual Client Configuration (Binary Installation)
- Download the binary for your operating system from the Releases page
- Configure your MCP client with the following settings:
{
"mcpServers": {
"BlazeMeter MCP": {
"command": "/path/to/bzm-mcp-binary",
"args": ["--mcp"],
"env": {
"BLAZEMETER_API_KEY": "/path/to/your/api-key.json"
}
}
}
}
Manual Client Configuration (From Remote Source Code)
- Prerequisites: uv and Python 3.11+
- Configure your MCP client with the following settings:
{
"mcpServers": {
"BlazeMeter MCP": {
"command": "uvx",
"args": [
"--from", "git+https://github.com/Blazemeter/bzm-mcp.git@v1.0.1",
"-q", "bzm-mcp", "--mcp"
],
"env": {
"BLAZEMETER_API_KEY": "/path/to/your/api-key.json"
}
}
}
}
Docker MCP Client Configuration
{
"mcpServers": {
"Docker BlazeMeter MCP": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--mount",
"type=bind,source=/path/to/your/test/files,target=/home/bzm-mcp/working_directory/",
"-e",
"API_KEY_ID=your_api_key_id",
"-e",
"API_KEY_SECRET=your_api_key_secret",
"-e",
"SOURCE_WORKING_DIRECTORY=/path/to/your/test/files",
"ghcr.io/blazemeter/bzm-mcp:latest"
]
}
}
}
Custom CA Certificates (Corporate Environments) for Docker
When you need this:
- Your organization uses self-signed certificates
- You're behind a corporate proxy with SSL inspection
- You have a custom Certificate Authority (CA)
- You encounter SSL certificate verification errors when running tests
Required Configuration:
When using custom CA certificate bundles, you must configure both:
- Certificate Volume Mount: Mount your custom CA certificate bundle into the container
- SSL_CERT_FILE Environment Variable: Explicitly set the
SSL_CERT_FILEenvironment variable to point to the certificate location inside the container
Example Configuration
{
"mcpServers": {
"Docker BlazeMeter MCP": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--mount",
"type=bind,source=/path/to/your/test/files,target=/home/bzm-mcp/working_directory/",
"-v",
"/path/to/your/ca-bundle.crt:/etc/ssl/certs/custom-ca-bundle.crt",
"-e",
"SSL_CERT_FILE=/etc/ssl/certs/custom-ca-bundle.crt",
"-e",
"API_KEY_ID=your_api_key_id",
"-e",
"API_KEY_SECRET=your_api_key_secret",
"-e",
"SOURCE_WORKING_DIRECTORY=/path/to/your/test/files",
"ghcr.io/blazemeter/bzm-mcp:latest"
]
}
}
}
Replace:
/path/to/your/ca-bundle.crtwith your host system's CA certificate file path- The container path
/etc/ssl/certs/custom-ca-bundle.crtcan be any path you prefer (just ensure it matchesSSL_CERT_FILE)
The
SSL_CERT_FILEenvironment variable must be set to point to your custom CA certificate bundle. Thehttpxlibrary automatically respects theSSL_CERT_FILEenvironment variable for SSL certificate verification.
License
This project is licensed under the Apache License, Version 2.0. Please refer to LICENSE for the full terms.
Support
- MCP Server Documentation: BlazeMeter MCP Server Guide
- API Documentation: BlazeMeter API Documentation
- Issues: GitHub Issues
- Support: Contact BlazeMeter support for enterprise assistance
Metadata
Release files for iflow-mcp-blazemeter-bzm-mcp 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| iflow_mcp_blazemeter_bzm_mcp-1.1.1.tar.gz | 552.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iflow_mcp_blazemeter_bzm_mcp-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / iflow_mcp_blazemeter_bzm_mcp-1.1.1.tar.gz
| Download URL | iflow_mcp_blazemeter_bzm_mcp-1.1.1.tar.gz |
|---|---|
| Size | 552.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
def28cd0c6dd135b752c1bfe1165576ee16fb2dfbc6472c5e87a0196747940a4
|
|
BLAKE2b-256 checksum How to use checksums |
20bf4d9e2e2d1f8e6209d15be73dd0dbbc57960837fb36df2428ad0d3d021b84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_blazemeter_bzm_mcp-1.1.1-py3-none-any.whl
| Download URL | iflow_mcp_blazemeter_bzm_mcp-1.1.1-py3-none-any.whl |
|---|---|
| Size | 643.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4719b4ad13924df8d056b9626c54d53f423d27c41dec68090320df08e328478e
|
|
BLAKE2b-256 checksum How to use checksums |
344ae07569419f555a00702e426fa11f63b56df0f6af327a447cdca6c7d8b8e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|