bzm-mcp

Provides an MCP server that lets AI tools manage end-to-end BlazeMeter performance testing workflows (create/execute/report) via natural-language interactions, using BlazeMeter API credentials configured through the MCP host.

Evaluated Mar 30, 2026 (21d ago)

Homepage ↗ Repo ↗ Ai Ml mcp-server model-context-protocol load-testing performance-testing blazemeter ai-integration python docker

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Uses API key credentials (key ID + secret) rather than OAuth; documentation emphasizes storing credentials in api-keys.json or environment variables and provides a mechanism for custom CA bundles (SSL_CERT_FILE) for corporate TLS inspection. No explicit guidance is provided about least-privilege scopes, secret rotation, or avoiding secret leakage in logs; dependency list exists but no vulnerability/CVE evidence is provided.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You already use BlazeMeter and want agent-driven orchestration of performance testing from an MCP-compatible environment.

Avoid When

You cannot securely manage/store BlazeMeter API credentials or you require an interface with strict REST/OpenAPI-only governance rather than MCP.

Use Cases

• Create and run BlazeMeter load/performance tests from an AI agent
• Generate performance reports and summaries after test runs
• Automate iterative tuning of test scenarios with conversational workflows
• Integrate performance testing into IDE-based agent workflows (Cursor/VS Code/Claude Desktop)

Not For

• A general-purpose BlazeMeter administration UI
• Direct execution of tests without an MCP-capable host/agent integration
• Use as a standalone load testing runner without MCP orchestration

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: BlazeMeter API key pair (API Key ID and Secret) for the underlying API calls Environment variable pointing to an api-keys.json file (BLAZEMETER_API_KEY) for binary installation/config

OAuth: No Scopes: No

Authentication is via BlazeMeter credentials provided either as an api-keys.json path (for the binary/CLI flow) or as API_KEY_ID/API_KEY_SECRET (for Docker). Documentation mentions an AI consent prerequisite.

Pricing

Free tier: No

Requires CC: No

No pricing details for the MCP server were provided; BlazeMeter usage costs would typically apply on the BlazeMeter side.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Requires an MCP-capable host (e.g., Cursor/VS Code/Claude Desktop) and correct mcpServers configuration.
⚠ Misconfigured credential paths/env vars (BLAZEMETER_API_KEY or API_KEY_ID/API_KEY_SECRET) will prevent successful calls to BlazeMeter.
⚠ Docker usage may require path/volume mounting and custom CA configuration in corporate environments.

Alternatives

BlazeMeter API (direct integration without MCP) CI/CD pipeline execution of BlazeMeter tests Other MCP servers or generic tool-call wrappers around BlazeMeter REST APIs

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for bzm-mcp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.