BlazeMeter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_workspacesC | Get workspaces from a specified account. |
| get_projectsC | Get projects from a specified workspace. |
| get_test_runsC | Get test runs (masters) for a specified test. |
| get_test_run_summaryC | Get the summary report for a specified test run (master). |
| get_test_run_aggregate_dataC | Get the aggregate report data for a specified test run (master). |
| get_test_run_errors_dataC | Get the errors report data for a specified test run (master). |
| get_test_run_thresholdsC | Get the thresholds report for a specified test run (master). |
| get_test_run_timeline_kpisB | Get the timeline KPIs report for a specified test run (master). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose targeting specific resources and report types. The six test run report tools (aggregate_data, errors_data, summary, thresholds, timeline_kpis) each retrieve different data slices without overlap, while get_projects and get_workspaces handle distinct workspace and account-level operations.
All tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming structure is perfectly predictable: get_[resource]_[optional_specific_data] (e.g., get_test_run_aggregate_data, get_workspaces).
Eight tools is reasonable for a performance testing domain, though slightly thin for complete lifecycle coverage. The tools focus heavily on retrieval operations for test runs and workspaces, which fits the server's apparent monitoring/reporting purpose but might benefit from additional test execution or configuration management tools.
The surface provides excellent read-only coverage for test run reports and workspace/project retrieval, but has notable gaps in test creation, execution, and management operations. Agents can query existing data but cannot initiate tests, modify configurations, or perform other essential performance testing workflow actions.