BlazeMeter 2.7 adds MCP Server search for tests and executions across the full account, giving release owners a faster way to locate performance evidence without project IDs or manual project-by-project navigation.
AI-assisted search across the test estate
The new MCP Server capabilities allow AI assistants to search BlazeMeter tests and executions using natural-language requests. For organizations with many workspaces, projects, owners, and historical runs, this changes a previously manual discovery task into a guided query workflow.
The supported search filters are:
- Workspace and project
- Owner and location
- Cloud provider
- Virtual users and duration
- Creation date and execution date
This is useful when a release manager needs to find the latest run for a service, compare prior load profiles, or identify tests owned by a specific team. It can reduce the time spent locating evidence during release reviews, incident analysis, and capacity planning.
Filter discovery reduces inaccurate queries
BlazeMeter 2.7 also lets an AI assistant retrieve valid filter values before it runs a search. Rather than guessing a workspace name, cloud-provider value, or owner identifier, the assistant can first determine what values are available.
For enterprise teams, this matters because inaccurate searches create more than minor friction. They can produce incomplete evidence, wasted engineering time, and inconsistent conclusions during release-governance reviews. Validated filters make AI-assisted retrieval more dependable and easier to standardize.
