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.
Controls should still be defined. Teams need clear decisions on which users and service identities may search account-wide test metadata, which MCP clients are approved, and how results are used in release decisions.
Optional telemetry supports operational oversight
The MCP Server now supports optional privacy-first telemetry powered by OpenTelemetry. It records operational signals such as:
- MCP tool usage
- Success and failure rates
- Response times
- MCP client type
The telemetry is designed not to collect sensitive data and can be disabled at any time. This gives platform owners a basis for assessing whether MCP usage is reliable and where users encounter errors or latency.
Telemetry controls need reviewed alongside existing observability and privacy standards. Security, compliance, and platform teams should document enablement decisions, retention expectations, and the accountable owner for reviewing usage data.
Taurus Cloud security remediation
BlazeMeter 2.7 includes Taurus Cloud version 2.4.444-reduced, which resolves identified high-severity vulnerabilities by applying fixes and removing affected components.
The addressed advisories are:
- CVE-2026-12151 affecting undici
- CVE-2026-49853 affecting tornado
- CVE-2026-49855 affecting tornado
- GHSA-537c-gmf6-5ccf affecting cryptography
- GHSA-6v7p-g79w-8964 affecting msgpack
For delivery leaders, the priority is not merely applying the updated version. Record the deployment scope, confirm the affected Taurus Cloud runtime is updated, and retain validation evidence for security and audit reporting. Where performance testing supports regulated or customer-facing releases, this evidence should be linked to the relevant change and release records.
Workflow and governance implications
BlazeMeter 2.7 can make performance-test discovery more accessible to teams that already use AI assistants, but access speed should not weaken delivery controls. A practical operating model includes:
- Approving MCP clients and authentication methods
- Defining account, workspace, and project access boundaries
- Establishing search-result handling expectations
- Monitoring telemetry only where policy permits
- Capturing Taurus Cloud update evidence in change records
This keeps the benefit focused on faster evidence retrieval while preserving accountability for test assets, execution history, and security posture.
How Merito helps
Merito helps enterprises introduce BlazeMeter capabilities within existing QA, DevOps, and DevSecOps governance. We can assess MCP access patterns, define telemetry and audit controls, plan Taurus Cloud updates, and connect performance-test evidence to release-management workflows.
The result is a controlled adoption path: teams gain faster test discovery, while leaders retain visibility into access, operational reliability, and remediation status.
Merito is an authorized Perforce reseller and services partner. Our Perforce BlazeMeter team can scope licensing, sizing, and rollout for 2.7, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.