blazemeter-explorer
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@blazemeter-explorer show vault settings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BlazeMeter Explorer MCP
An MCP server for the public Swagger document served by BlazeMeter's API v4 explorer. It is a companion to, not a replacement for, the official BlazeMeter MCP.
Why this exists
The official server is an opinionated performance-testing workflow layer: its nine tool groups cover accounts, billing, executions, help, projects, skills, tests, users, and workspaces. The public explorer is a different, smaller API surface: 54 operations across 49 paths, mainly user/session, vault settings, RSS feed, static frontend asset, and CSP-report routes. It does not document the official server's core /accounts, /workspaces, /projects, /tests, or /masters operations.
This server makes that explorer surface queryable without pretending that its documentation is a complete BlazeMeter API reference.
Related MCP server: Britive MCP Server
Install
{
"mcpServers": {
"blazemeter-explorer": {
"command": "uvx",
"args": ["--from", "git+https://github.com/aminamos/blazemeter-explorer-mcp.git", "blazemeter-explorer-mcp"],
"env": {
"BLAZEMETER_API_KEY_ID": "your-key-id",
"BLAZEMETER_API_KEY_SECRET": "your-key-secret"
}
}
}
}The server reads credentials only from environment variables and sends them as HTTP Basic authentication, matching BlazeMeter's official MCP convention. Do not put credentials in prompts or tool arguments.
Tools
list_operations: compact catalog of the checked-in OpenAPI operations.get_operation: full parameter and response metadata for anoperation_id.invoke_operation: executes one documented operation. POST, PUT, PATCH, and DELETE calls return a confirmation response untilconfirm=trueis supplied.
Spec provenance and refresh
openapi/blazemeter-v4-explorer.swagger.json was retrieved from https://a.blazemeter.com/api/v4/explorer/swagger.json on 2026-07-22. It is checked in so clients have a reviewable, reproducible catalog. Refresh it with:
Invoke-WebRequest https://a.blazemeter.com/api/v4/explorer/swagger.json -OutFile openapi/blazemeter-v4-explorer.swagger.jsonReview the diff before committing a refresh: the public explorer can change independently from the official MCP.
Comparison
Aspect | Official | This companion |
Source of truth | Curated Python workflow implementation | Public explorer Swagger document |
Shape | Nine high-level, domain-specific tool groups | Three generic spec discovery/invocation tools |
Core load testing | Creates/configures/tests/runs/analyzes reports | Not documented in this Swagger document |
Explorer-only value | No direct surface for these operations | Vault settings, BZM session inactivity, user UI messages, RSS feeds, static asset and CSP routes |
Write safety | Official server has its own confirmation mode | Explicit |
Development
uv sync --group dev
uv run pytestThis is an independent, unofficial project. BlazeMeter names and APIs belong to their respective owners.
Available Tools
3 toolsget_operationB
Get parameters and response schemas for one public explorer operation.
Inputs: operation_id (required). Returns: object
invoke_operationA
Call one documented explorer operation. Writes require explicit confirm=true.
Inputs: operation_id (required), body, query, confirm, +1 more. Returns: object
list_operationsA
List all operations in the checked-in public BlazeMeter v4 explorer spec.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool serves a distinct phase in the workflow: listing available operations, retrieving details for a specific operation, and invoking an operation. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: list_operations, get_operation, invoke_operation. This is predictable and easy to understand.
With only 3 tools, the set is minimal but well-aligned with the server's purpose of exploring and invoking operations. It is on the lower end of the ideal range but not insufficient.
The tool set covers the complete lifecycle for its domain: discover operations (list), understand operations (get), and execute operations (invoke). No obvious gaps for the stated purpose of an explorer.
Related MCP Connectors
Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.
OCPI versions, checks and payload validation, plus your own test runs and run starts with a key.
Build and manage Elasticsearch REST APIs: models, endpoints, API keys and deploys.
Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables querying and exploring Cribl Stream and Edge deployments, providing access to worker groups, fleets, sources, destinations, pipelines, routes, event breakers, and lookups through a structured interface.73MIT No Attribution

Britive MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.1-- AlicenseBqualityDmaintenanceEnables automated deployments, environment management, snapshots, and deployment monitoring through DevOps Deploy's REST API.15MIT
- AlicenseBqualityDmaintenanceExposes any GraphQL API as a single tool for executing queries and mutations with authentication support.1MIT