mcp-perf-suite

Manage the PerfMemory lessons-learned layer — search for past fixes before debugging, store debug sessions and attempts during debugging, and ingest existing knowledge from debug manifests or lessons-learned documents. Use when the user mentions perfmemory, lessons learned, debug memory, ingesting debug manifests, or searching for past fixes.

Upload performance test artifacts to SharePoint document libraries. Use when the user mentions uploading artifacts to SharePoint, saving test results to SharePoint, persisting files to SharePoint, or archiving performance test output.

Iterative AI-driven JMeter script debugging via smoke tests, log analysis, and targeted fixes. Use when the user asks to debug, troubleshoot, fix errors in, or validate a JMeter script, or mentions JMeter smoke testing failures.

Diagnose and fix JMeter script failures in Microsoft Entra ID (Azure AD) authentication flows including OAuth2/OIDC authorize, WS-Federation, OpenAM, and Kerberos SSO. Use when debugging JMeter scripts that interact with login.microsoftonline.com, EntraID, Entra ID, Azure AD, WS-Federation, wsfed, OpenAM, BssoInterrupt, MSAL, ConvergedSignIn, GetCredentialType, flowToken, ESTSWCTXFLOWTOKEN, or any Microsoft identity platform login flow.

Convert HAR (HTTP Archive) files into JMeter JMX scripts. Use when the user mentions HAR files, HAR conversion, Chrome DevTools recording, Fiddler capture, mitmproxy, Postman export, or creating a JMeter script from browser network traffic.

AI-assisted Human-in-the-Loop JMeter script analysis, component addition, editing, and headless smoke testing. Use when the user wants to analyze, edit, add components to, import, or modify a JMeter JMX script, or run a local JMeter smoke test.

Orchestrate MS Teams notifications for performance testing — send start-test, stop-test, and test-results notifications to configured channels and chats using templates, @mentions, and auto-populated context from test artifacts. Use when the user mentions Teams notification, notify the team, send Teams message, start/stop test notification, test results notification, or MS Teams alert.

Validate existing JMeter scripts via autonomous smoke testing using the jmeter-script-validator subagent. Use when the user mentions script validation, script health check, validate JMeter script, re-validate old scripts, check if a JMeter script still works, or smoke test validation. This skill orchestrates one or more validator subagents, each producing a standalone Markdown validation report.

Orchestrates BlazeMeter and Datadog data extraction using dedicated subagents. Use when the user mentions subagent workflow, subagent orchestrator, or wants to run the BlazeMeter and Datadog extraction phases via subagents. This skill handles the extraction and handoff phases only — it does NOT run PerfAnalysis, PerfReport, or Confluence. After this skill completes, the user can continue with the performance-testing-workflow skill starting from Step 4 (PerfAnalysis).

Create comparison reports analyzing multiple test runs side-by-side with comparison charts and optional Confluence publishing. Use when the user mentions comparison report, multi-run comparison, side-by-side analysis, or comparing test runs.

AI-assisted HITL revision of performance test reports with iterative refinement, version tracking, and optional Confluence publishing. Use when the user mentions report revision, AI-enhanced report, revise executive summary, revise key observations, revise issues table, or improve a performance report.

End-to-end performance testing pipeline orchestrating BlazeMeter, Datadog, PerfAnalysis, PerfReport, and Confluence MCP workflows sequentially. Use when the user mentions performance testing workflow, E2E pipeline, BlazeMeter results, test run analysis, performance report generation, or end-to-end test processing.

Run Playwright browser automation to capture network traffic and generate a JMeter JMX script. Use when the user mentions browser automation, Playwright recording, test spec execution, browser-based network capture, or generating a JMeter script from a live browser session.

Convert Azure DevOps (ADO) QA Functional test cases into browser automation Markdown specs for JMeter MCP. Use when the user mentions ADO test cases, Azure DevOps conversion, QA functional to performance, or test case format migration.

Convert Swagger 2.x or OpenAPI 3.x specification files into JMeter JMX scripts. Use when the user mentions Swagger, OpenAPI, API spec conversion, or creating a JMeter script from an API specification file.

Review, adjust, or generate JMeter correlation variable names from correlation_spec.json files. Use when working with correlation_naming.json, correlation specs, JMeter variable naming, or when the user mentions correlation naming, variable mapping, or correlation review.