Bzm MCP Server

The BlazeMeter MCP Server connects AI tools directly to BlazeMeter's cloud-based performance testing platform. This gives AI agents, assistants, and

Local serverstdioPython

What is the Bzm MCP MCP server?

Bzm MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. 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.

Setting it up

installs on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 6 environment variables: BLAZEMETER_API_KEY, OTEL_SDK_DISABLED, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_PROTOCOL, API_KEY_ID, API_KEY_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • 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)

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by blazemeter; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the bzm mcp mcp server does with a few real requests.

How to install the Bzm MCP MCP server

{
  "mcpServers": {
    "BlazeMeter MCP": {
      "command": "/path/to/bzm-mcp-binary",
      "args": ["--mcp"],
      "env": {
        "BLAZEMETER_API_KEY": "/path/to/your/api-key.json"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • 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)
VariableDescriptionRequired
BLAZEMETER_API_KEYCredential the server authenticates with.Yes
OTEL_SDK_DISABLEDConfiguration value read at startup.Optional
OTEL_EXPORTER_OTLP_ENDPOINTConfiguration value read at startup.Optional
OTEL_EXPORTER_OTLP_PROTOCOLConfiguration value read at startup.Optional
API_KEY_IDCredential the server authenticates with.Yes
API_KEY_SECRETCredential the server authenticates with.Yes

Frequently asked questions

It connects Bzm MCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Bzm MCP directly.