OctoPerf — Claude Code plugins
Claude Code plugin marketplace for the OctoPerf load-testing platform.
Not using Claude Code? The OctoPerf MCP server is a hosted, client-agnostic remote server (
https://api.octoperf.com/mcp, Streamable HTTP, OAuth 2.1 — no API key). It works with any MCP client. This repo is just the one-step Claude Code entry point — see Other clients below.
This repo distributes one plugin (octoperf) that:
- registers the hosted OctoPerf MCP server (
https://api.octoperf.com/mcp, Streamable HTTP, OAuth 2.1 + PKCE + DCR — no API key); - installs twenty workflow skills that drive the MCP tools end-to-end (recording & import, migration from BlazeMeter / LoadRunner / NeoLoad, correlation, validation, scenario composition, SLAs, monitoring, bench reports, scheduling, notifications, on-premise agents, workspaces…);
- ships an
AGENTS.mdreference describing every MCP tool the server exposes.
Install
/plugin marketplace add OctoPerf/octoperf-claude-plugins
/plugin install octoperf@octoperf
The first MCP call opens a browser for OAuth login on api.octoperf.com.
Revoke at any time from Account → Connected applications on OctoPerf.
What you get
| Component | Location | Purpose |
|---|---|---|
| MCP server | plugins/octoperf/.mcp.json | Tools to manage workspaces, projects, VUs, scenarios, bench results |
| AGENTS.md | plugins/octoperf/AGENTS.md | Full MCP tool catalogue (also served as octoperf://templates/agents-md) |
| Skills | plugins/octoperf/skills/*/SKILL.md | Workflow recipes invoked on natural-language triggers |
Skills
| Skill | Triggers on |
|---|---|
octoperf-har-recording | "record my application", "capture a HAR", "import this .har" |
octoperf-jtl-import | "import my JTL", "analyse these JMeter results" |
octoperf-blazemeter-migration | "migrate from BlazeMeter", "convert my Taurus test" |
octoperf-loadrunner-migration | "migrate from LoadRunner", "convert a .usr script" |
octoperf-neoload-migration | "migrate from NeoLoad", "convert a .nlp project" |
octoperf-auto-correlation | "correlate the VU", "fix replay errors", "401/403 on replay" |
octoperf-validation-triage | "the validation is red", "lots of errors after import" |
octoperf-scenario-composition | "build a scenario", "ramp-up / load shape", "user profiles" |
octoperf-sla | "define an SLA", "fail the test if response time > X" |
octoperf-monitoring | "monitor my servers during the test", "add a database monitor" |
octoperf-scenario-diagnosis | "the load test failed", "why are response times so high" |
octoperf-bench-reports | "what's the right tool for this widget", widget metric questions |
octoperf-report-item-editing | "change the metrics of this report widget", "add a filter" |
octoperf-export-bench-report-pdf | "export the report as PDF", "print the bench report" |
octoperf-real-browser-probe | "EUM probe", "Playwright probe", "TruClient equivalent" |
octoperf-scheduling | "schedule the scenario", "run every weekday at 8am" |
octoperf-notifications | "notify Slack when a test fails", "open a JIRA ticket on failure" |
octoperf-onpremise-agent | "run from my own machines", "install an on-premise agent" |
octoperf-workspace | "add someone to the workspace", "change member permissions" |
octoperf-async-polling | invoked automatically by any skill that has to poll a taskId result |
Other clients
The MCP server is not Claude-specific. To connect Claude.ai, Claude Desktop,
Cursor, ChatGPT, Codex, Gemini CLI, GitHub Copilot — or any other MCP client —
see the MCP server documentation. Most
clients just need the server URL https://api.octoperf.com/mcp.
License
Apache-2.0