Skip to content

1.2.0

Choose a tag to compare

View all tags
@Baraujo25 Baraujo25 released this 22 Apr 20:25
v1.2.0
beb0dd9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's new on the BlazeMeter MCP

Failure criteria

  • Read failure criteria on tests with a structured domain model and human-friendly labels (KPIs, operators, and rule fields) so agents can explain thresholds without exposing raw API codes first.
  • failure_criteria_meta — local, read-only catalog of KPIs, conditions, and rule fields (no BlazeMeter API call); use it to build valid rules before configuring.
  • configure_failure_criteria — set or replace the full failure-criteria ruleset for a test (enable/disable, thresholds, sliding windows, stop-on-violation, and related options), with merge guidance when preserving existing rules.

Execution reporting and AI-assisted insights

  • ai_analysis on the execution tool — start or poll BlazeMeter AI analysis for a finished (or running) execution; responses indicate when results are ready vs. still processing.
  • read_anomalies_stats — anomaly statistics for an execution (status, counts, affected labels, per-anomaly context for LLMs), with clearer formatting and behavior when stats are unavailable for the account.
  • read_summary — structured summary reports with normalized field names, metric explanations, and guidance aimed at better AI interpretation and troubleshooting (including pointers to relevant Skills where appropriate).
  • read_errors and read_request_stats — richer, more consistent formatting and context for agents; improved handling when report data is not available (including archived executions).
  • read_all_reports — simplified aggregation of summary, errors, and request stats in one call.

Reliability, security, and compliance

  • Stronger validation and alignment with documented tool/action schemas across managers (reduces invalid or ambiguous MCP calls).
  • Security-focused hardening: safer handling of paths and HTML in help, traceback sanitization, token and HTTP request constraints, skills and upload paths, and expanded automated tests (including Windows in CI where applicable).
  • Dependency updates, including MCP stack CVE remediation and refreshed lockfile; python-multipart bump.
  • Mend (SCA) scanning in CI

Developer and distribution experience

  • Deeplink install — one-click style links on README.md to add the MCP in supported clients (e.g. Cursor, VS Code).
  • Docker — image pull policy updated so runs use always pull for fresher images.
  • Project hygiene — updated license, SECURITY.md (clearer reporting process), logo, and Node.js 24 in GitHub Actions.

Full Changelog: v1.1.1...v1.2.0

Assets 7
Loading