Experimental MCP server that writes, validates and runs k6 load tests locally and searches the k6 docs.

How it works

Foe: Storm Elemental, an outage, a failed deploy or a slow pipeline.

Foes

  • Storm Elemental

Party · Context

  • SentinelYour agent100/100
  1. Storm Elemental

    The Storm Elemental blocks the way.

    What really happensIt stands for an outage, a failed deploy or a slow pipeline.

    Sentinel: Context 100/100.

  2. Lightning

    Lightning splits the sky and the servers go dark.

    What really happensAn outage or a broken pipeline stops everything until someone finds the cause.

    Sentinel takes 7. Sentinel takes 7. Sentinel: Context 86/100.

  3. Grafana k6 MCP Server

    The k6 drum is set up in a Docker tent.

    What really happensClaude Code starts the grafana/mcp-k6 image over stdio. The image includes k6, so nothing else is needed.

    Storm Elemental takes 31.

  4. Grafana k6 MCP Server

    A battle plan is written in plain words.

    What really happensThe generate_script prompt drafts a k6 test from your requirements, using k6 best practices and the official docs.

    Storm Elemental takes 21.

  5. Lightning

    The Storm Elemental uses Lightning.

    Sentinel takes 7. Sentinel takes 7. Sentinel: Context 72/100.

  6. Grafana k6 MCP Server

    One scout runs the route before the crowd marches.

    What really happensvalidate_script runs the script with 1 virtual user and 1 iteration and returns errors to fix.

    Storm Elemental takes 14.

  7. Grafana k6 MCP Server

    The drum sounds, and the crowd surges at the gates.

    What really happensrun_script runs the load test locally with your VUs, duration or iterations and pulls insights from the results.

    Storm Elemental takes 34. Storm Elemental falls.

  8. Victory

    The Storm Elemental falls.

Learn this spell

Claude Code

claude mcp add --scope=user --transport=stdio k6 -- docker run --rm -i grafana/mcp-k6

Codex

No one-line setup. Follow the source's instructions.

Notes

Marked experimental. The Docker image includes k6; Homebrew and native installs use claude mcp add --scope=user --transport=stdio k6 mcp-k6. validate_script runs a script with 1 VU and 1 iteration, run_script runs a local test with optional VU, duration and iteration overrides, and the generate_script prompt drafts tests from plain-English requirements. The README gives a JSON config for Codex CLI. A shared deployment has no built-in authentication. Load tests send real traffic, so aim them at systems you run.

This spell has no recorded sessions in the curator's logs. Tried it? Send a spell report.