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:

1. Download the appropriate binary for your operating system from the Releases page

Manual Client Configuration (Binary Installation)

1. Download the binary for your operating system from the Releases page

2. Run the binary once — it will print a JSON config and clickable links to add this MCP in Cursor or VS Code.

3. Or configure your MCP client manually 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)

1. Prerequisites: uv and Python 3.11+

2. One-click install or configure your MCP client manually:

After installing, set BLAZEMETER_API_KEY to your api-key.json path in your client's MCP settings.

Or configure manually with the following settings:

{
  "mcpServers": {
    "BlazeMeter MCP": {
      "command": "uvx",
      "args": [
        "--from", "git+https://github.com/Blazemeter/bzm-mcp.git@v1.3.1",
        "-q", "bzm-mcp", "--mcp"
      ],
      "env": {
        "BLAZEMETER_API_KEY": "/path/to/your/api-key.json"
      }
    }
  }
}

Docker MCP Client Configuration

1. Prerequisites: Docker

After installing, set API_KEY_ID, API_KEY_SECRET, and optionally mount/working dir in your client's MCP settings.

{
  "mcpServers": {
    "Docker BlazeMeter MCP": {
      "command": "docker",
      "args": [
        "run",
        "--pull=always",
        "--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:

1. Certificate Volume Mount: Mount your custom CA certificate bundle into the container

2. SSL_CERT_FILE Environment Variable: Explicitly set the SSL_CERT_FILE environment variable to point to the certificate location inside the container

{
  "mcpServers": {
    "Docker BlazeMeter MCP": {
      "command": "docker",
      "args": [
        "run",
        "--pull=always",
        "--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.crt with your host system's CA certificate file path

• The container path /etc/ssl/certs/custom-ca-bundle.crt can be any path you prefer (just ensure it matches SSL_CERT_FILE)

The SSL_CERT_FILE environment variable must be set to point to your custom CA certificate bundle. The httpx library automatically respects the SSL_CERT_FILE environment variable for SSL certificate verification.

OpenTelemetry

BlazeMeter MCP reports traces and metrics for MCP tool calls using OpenTelemetry. This gives you visibility into which tools are used, how long they take, and when errors occur.

Telemetry is enabled by default. You do not need to configure anything unless you want to change where data is sent or turn it off.

Default behavior

By default, telemetry is exported over gRPC to:

https://grpc.public.prd.shared.perforce.com

The service is identified as bzm-mcp with the current release version. If telemetry fails to start or export, the MCP server continues to work as usual.

Turn off telemetry

Add OTEL_SDK_DISABLED=true to your MCP client environment:

"env": {
  "OTEL_SDK_DISABLED": "true"
}

For Docker, pass it with -e:

"-e",
"OTEL_SDK_DISABLED=true"

You can also pass --no-telemetry on the command line (binary or uvx install):

"args": ["--mcp", "--no-telemetry"]

Send data to your own collector

Use these environment variables to point at a different OpenTelemetry collector (for example, a local one during development):

gRPC example (typical local collector on port 4317):

"env": {
  "OTEL_EXPORTER_OTLP_ENDPOINT": "http://localhost:4317",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "grpc"
}

HTTP example (typical local collector on port 4318):

"env": {
  "OTEL_EXPORTER_OTLP_ENDPOINT": "http://localhost:4318",
  "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf"
}

When running the binary directly, you can override the endpoint and headers with CLI flags instead of environment variables:

"args": [
  "--mcp",
  "--otel-endpoint", "http://localhost:4317",
  "--otel-headers", "Authorization=Bearer token"
]

What gets reported

Each MCP tool call creates:

• Traces — one span per call with the tool name, action, MCP client name and version, session ID, and error type when applicable.

• Metrics — mcp.tool.calls (count) and mcp.tool.duration (seconds), broken down by tool and action.

Security tokens and other credentials are not included in telemetry data.

If your MCP client sends traceparent or tracestate in the request metadata, BlazeMeter MCP links its spans to that parent trace.

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