Click on "Install 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.
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.
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: MCP OpenAPI Discovery
{
"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.
list_operations: compact catalog of the checked-in OpenAPI operations.
get_operation: full parameter and response metadata for an operation_id.
invoke_operation: executes one documented operation. POST, PUT, PATCH, and DELETE calls return a confirmation response until confirm=true is supplied.
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.
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 |
uv sync --group dev
uv run pytestThis is an independent, unofficial project. BlazeMeter names and APIs belong to their respective owners.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Search, document and execute authenticated API calls across 700+ apps via one MCP server
34 production API tools over one hosted MCP endpoint.
Build and manage Cloudgate workflow-APIs: controllers, actions, workflow graphs, and databases.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aminamos/blazemeter-explorer-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server