Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Artillery MCP

by kosiakMDversion 0.1.7i★ 0iRuns on your computerRepository ↗
Registry nameio.github.kosiakMD/artillery-mcp

How to install

What it does

MCP server for Artillery 2.x — full flags, Fargate, raw-text parser, project launcher (MIT)

  • Connects Runs on your computer
  • Account or key Needs ARTILLERY_CLOUD_API_KEY
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness3/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score3/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Artillery MCP. Follow https://mcp.popnx.com/i/kosiakmd-artillery-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Artillery MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Artillery MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "artillery": { "command": "npx", "args": [ "-y", "@kosiakmd/artillery-mcp" ], "env": { "ARTILLERY_CLOUD_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ARTILLERY_CLOUD_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Artillery MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Artillery MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "artillery": {
          "command": "npx",
          "args": [
            "-y",
            "@kosiakmd/artillery-mcp"
          ],
          "env": {
            "ARTILLERY_CLOUD_API_KEY": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use Artillery MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Artillery MCP or shows a Artillery MCP tool in the answer, you are connected

3 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • ARTILLERY_WORKDIR Absolute path to project root (walk-up from here finds .artillery-mcp.config.json).
  • ARTILLERY_MCP_CONFIG Absolute path to .artillery-mcp.config.json. Enables run_project_lt + counterBreakdown when set.
  • ARTILLERY_TIMEOUT_MS Max duration of a single artillery command. Default 1800000 (30min).

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Artillery MCP yet

Artillery MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Artillery MCP

  • You need a Artillery MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Artillery MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Artillery MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Artillery MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Artillery MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Artillery MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user artillery --env ARTILLERY_CLOUD_API_KEY=your-value -- npx -y @kosiakmd/artillery-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ARTILLERY_CLOUD_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Artillery MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Artillery MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user artillery --env ARTILLERY_CLOUD_API_KEY=your-value -- npx -y @kosiakmd/artillery-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see Artillery MCP listed as connected

  6. Try it

    Use Artillery MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Artillery MCP or shows a Artillery MCP tool in the answer, you are connected

3 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • ARTILLERY_WORKDIR Absolute path to project root (walk-up from here finds .artillery-mcp.config.json).
  • ARTILLERY_MCP_CONFIG Absolute path to .artillery-mcp.config.json. Enables run_project_lt + counterBreakdown when set.
  • ARTILLERY_TIMEOUT_MS Max duration of a single artillery command. Default 1800000 (30min).

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Artillery MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Artillery MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "artillery": { "command": "npx", "args": [ "-y", "@kosiakmd/artillery-mcp" ], "env": { "ARTILLERY_CLOUD_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ARTILLERY_CLOUD_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Artillery MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Artillery MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Artillery MCP settings, ARTILLERY_CLOUD_API_KEY is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Artillery MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Artillery MCP or shows a Artillery MCP tool in the answer, you are connected

3 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • ARTILLERY_WORKDIR Absolute path to project root (walk-up from here finds .artillery-mcp.config.json).
  • ARTILLERY_MCP_CONFIG Absolute path to .artillery-mcp.config.json. Enables run_project_lt + counterBreakdown when set.
  • ARTILLERY_TIMEOUT_MS Max duration of a single artillery command. Default 1800000 (30min).

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Artillery MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Artillery MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "artillery": { "type": "stdio", "command": "npx", "args": [ "-y", "@kosiakmd/artillery-mcp" ], "env": { "ARTILLERY_CLOUD_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ARTILLERY_CLOUD_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Artillery MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Artillery MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Artillery MCP settings, ARTILLERY_CLOUD_API_KEY is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Artillery MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Artillery MCP or shows a Artillery MCP tool in the answer, you are connected

3 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • ARTILLERY_WORKDIR Absolute path to project root (walk-up from here finds .artillery-mcp.config.json).
  • ARTILLERY_MCP_CONFIG Absolute path to .artillery-mcp.config.json. Enables run_project_lt + counterBreakdown when set.
  • ARTILLERY_TIMEOUT_MS Max duration of a single artillery command. Default 1800000 (30min).

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Artillery MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user artillery --env ARTILLERY_CLOUD_API_KEY=your-value -- npx -y @kosiakmd/artillery-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "artillery": {
      "command": "npx",
      "args": [
        "-y",
        "@kosiakmd/artillery-mcp"
      ],
      "env": {
        "ARTILLERY_CLOUD_API_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "artillery": {
      "command": "npx",
      "args": [
        "-y",
        "@kosiakmd/artillery-mcp"
      ],
      "env": {
        "ARTILLERY_CLOUD_API_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "artillery": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@kosiakmd/artillery-mcp"
      ],
      "env": {
        "ARTILLERY_CLOUD_API_KEY": "your-value"
      }
    }
  }
}

Values you fill in

  • ARTILLERY_WORKDIR env
    Absolute path to project root (walk-up from here finds .artillery-mcp.config.json).
  • ARTILLERY_CLOUD_API_KEY secret required env
    Artillery Cloud API key. Forwarded to artillery CLI when record=true.
  • ARTILLERY_MCP_CONFIG env
    Absolute path to .artillery-mcp.config.json. Enables run_project_lt + counterBreakdown when set.
  • ARTILLERY_TIMEOUT_MS env
    Max duration of a single artillery command. Default 1800000 (30min).

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
113/wk
Connection
Runs on your computer
Latest versioni
0.1.7
Categoryi
Other
Published to registryi
Apr 15, 2026
Code last changedi
Jul 21, 2026
Maker
kosiakMD
Packages
npm: @kosiakmd/artillery-mcp
oci: docker.io/kosiakmd/artillery-mcp:0.1.7
oci: ghcr.io/kosiakmd/artillery-mcp:0.1.7
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account kosiakMD, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 4 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @kosiakmd/artillery-mcp@0.1.7

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/kosiakmd-artillery-mcp.svg)](https://mcp.popnx.com/en/servers/kosiakmd-artillery-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20815 servers in this category
  • Published to the registry more recently than 4% of the other 20815 servers in this category
  • Basic checks equal to or better than 99% of the other 20815 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Artillery MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ARTILLERY_CLOUD_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 4 months ago, and the latest version (0.1.7) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 4 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 31 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Artillery MCP
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@kosiakmd/artillery-mcp

Richer drop-in MCP server for Artillery 2.x — exposes the full artillery run and artillery run-fargate flag surface, parses raw text output (artillery-output.txt), returns every counter/rate/summary Artillery produces (not just http.*), and optionally adds a config-driven project launcher and counter-grouping for your custom counters.

Why another MCP server?

The upstream @jch1887/artillery-mcp-server was a solid start but missed several flags our team needed day-to-day. This package is a MIT-licensed fork with broader coverage. See Credits.

Featureupstreamthis package
run_test_from_file flagspath + output only+ --record/--key/--tags/--name/--note/-t/-e/--scenario-name/-v/--overrides/-p/--dotenv/-k/--count/-s
AWS Fargate (run-fargate)❌✅ full flag set
parse_results countershttp.* onlyALL counters + rates + nested summaries
Parse raw stdout (artillery-output.txt)❌✅ read_artillery_output tool
HTML report generationpasses invalid --report flag✅ separate artillery report call
Standalone JSON → HTML (run_report)❌✅
--dry-run validationbroken (flag doesn't exist in 2.x)✅ client-side YAML structural check
Opt-in project launcher❌✅ run_project_lt (when config present)
Opt-in counter grouping❌✅ counterBreakdown (when config present)
init scaffolder❌✅ npx @kosiakmd/artillery-mcp init
Shipped SKILL.md template❌✅ agent-oriented guidance
Docker image❌✅ multi-arch (Docker Hub + GHCR)
MCP Registry listing❌✅ io.github.kosiakMD/artillery-mcp
serverVersion accuracyhardcoded✅ read from package.json at runtime
Tests122163

Quickstart for agents (Claude Code / Cursor)

# In your project root

npx @kosiakmd/artillery-mcp init

Scaffolds two files (skipped if they already exist, use --force to overwrite):

  • .artillery-mcp.config.json — starter template with commented fields
  • .ai/skills/artillery-mcp/SKILL.md — agent-oriented guidance (when to call which tool, common patterns, gotchas)

After editing the config with your real flows/paths, register the MCP in your agent and restart the session:

claude mcp add artillery-mcp -s user \

-e ARTILLERY_WORKDIR="$PWD" \ -e ARTILLERY_CLOUD_API_KEY=a9_... \ -- npx -y @kosiakmd/artillery-mcp

Install / Quickstart (zero-config)

Runs out of the box — no config file needed. Works as an MCP server over stdio for Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.

# Using npx (no install)

npx -y @kosiakmd/artillery-mcp

Or install globally

npm install -g @kosiakmd/artillery-mcp artillery-mcp

Claude Code / Cursor — register as an MCP server in your client config:

{

"mcpServers": { "artillery-mcp": { "command": "npx", "args": ["-y", "@kosiakmd/artillery-mcp"], "env": { "ARTILLERY_WORKDIR": "/absolute/path/to/your/project", "ARTILLERY_CLOUD_API_KEY": "a9_..." } } } }

Claude Code CLI:

claude mcp add artillery-mcp -s user \

-e ARTILLERY_WORKDIR=/abs/path/to/project \ -e ARTILLERY_CLOUD_API_KEY=a9_... \ -- npx -y @kosiakmd/artillery-mcp

Prerequisites: Node.js ≥ 20; Artillery CLI on PATH (npm i -g artillery).

Docker

Multi-arch image — linux/amd64 and linux/arm64, Artillery CLI preinstalled. ~500 MB (Chromium/Playwright browsers skipped — see below). Published to both Docker Hub and GitHub Container Registry from the same build; identical digests.

# Docker Hub (discoverable via `docker search artillery-mcp`)

docker pull kosiakmd/artillery-mcp:latest

GitHub Container Registry

docker pull ghcr.io/kosiakmd/artillery-mcp:latest

Run (mount your project as /workspace):

docker run -i --init --rm \

-v "$PWD":/workspace \ -e ARTILLERY_CLOUD_API_KEY="$ARTILLERY_CLOUD_API_KEY" \ kosiakmd/artillery-mcp:latest

--init ensures the Node process gets reaped on stdin close. Mount /workspace read-write if you want save_config tools to persist to /workspace/saved-configs/; read-only is fine otherwise (the save-config family will simply return errors when called).

MCP client config (Claude Desktop / Cursor) — point the MCP at docker instead of npx:

{

"mcpServers": { "artillery-mcp": { "command": "docker", "args": [ "run", "-i", "--init", "--rm", "-v", "/absolute/path/to/your/project:/workspace", "-e", "ARTILLERY_CLOUD_API_KEY", "kosiakmd/artillery-mcp:latest" ], "env": { "ARTILLERY_CLOUD_API_KEY": "a9_..." } } } }

Playwright engine? If you use engine: playwright in your Artillery scripts, extend the base image with Chromium:

FROM kosiakmd/artillery-mcp:latest

ENV PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=0 RUN apk add --no-cache chromium nss freetype harfbuzz ttf-freefont \ && npm i -g @playwright/test \ && npx playwright install chromium

Image tags:

  • latest — most recent release
  • v0.1.1, v0.1, v0 — pinned by semver (patch / minor / major)

Environment variables

VarPurposeDefault
ARTILLERY_BINPath to artillery binaryauto-detected via which artillery
ARTILLERY_WORKDIRWorking directory for runscwd
ARTILLERY_TIMEOUT_MSMax duration of a single run1800000 (30 min)
ARTILLERY_MAX_OUTPUT_MBCap on captured stdout/stderr10
ARTILLERY_ALLOW_QUICKEnable quick_test tooltrue
ARTILLERY_CLOUD_API_KEYUsed when a tool is called with record: true—
ARTILLERY_MCP_CONFIGAbsolute path to project config (opt-in)—
DEBUGartillery:mcp:* for verbose logs—

18 base tools (no config needed)

Run tests

  • `run_test_from_file` — full-flag artillery run wrapper (see flag surface above).
  • `run_test_inline` — same but takes YAML text, writes to a tmp file.
  • `quick_test` — artillery quick with rate/count/duration/method/headers/body.
  • `run_fargate` — artillery run-fargate with --region, --cluster, --cpu, --memory, --launch-type, --spot, --subnet-ids, --security-group-ids, --task-role-name, --task-ephemeral-storage, --container-dns-servers, --max-duration, --packages, --secret, --no-assign-public-ip + all run-shared flags.
  • `run_preset_test` — smoke / baseline / soak / spike presets against a URL.
  • `run_saved_config` — re-run a saved config by name.

Parse + inspect results

  • `parse_results` — reads an Artillery JSON report; returns summary + allCounters + allRates + allSummaries + scenarios + metadata.
  • `read_artillery_output` — reads a raw Artillery stdout dump (e.g. artillery-output.txt saved from CI), returns rawText (with tail-truncation), summaryBlock, counters, rates, metrics (nested percentiles).
  • `run_report` — converts an existing JSON results file to HTML via artillery report. Use when you have JSON from CI artifacts and want shareable HTML without re-running.
  • `compare_results` — diff two Artillery JSON results for regression detection.

Saved configs

  • `save_config` / `list_configs` / `get_config` / `delete_config` — persistent named Artillery configs.

Interactive builder

  • `wizard_start` / `wizard_step` / `wizard_finalize` — interactive test builder.

Meta

  • `list_capabilities` — versions of Artillery/Node/this server, configured paths, limits.

Optional feature #1 — Project launcher (run_project_lt)

Activated when a .artillery-mcp.config.json file is discovered. Gives you one-liner invocations instead of writing full artillery run ... flag lists.

Discovery precedence:

  1. ARTILLERY_MCP_CONFIG env var (absolute path)
  2. Walk up from ARTILLERY_WORKDIR / cwd looking for .artillery-mcp.config.json
  3. No config → this tool is not registered

Config (.artillery-mcp.config.json):

{

"flows": { "browse": "tests/load/browse.yml", "buy": "tests/load/buy.yml", "combined": "tests/load/combined.yml" }, "environments": ["local", "staging", "prod"], "defaultTags": { "repo": "my-app", "owner": "Platform" }, "tagTemplates": ["type:{flow}", "env:{env}", "source:mcp"], "outputDir": "load-test-results" }

Call:

{ "flow": "buy", "environment": "staging", "note": "canary v42" }

Effective command:

artillery run \

--record \ --name "buy-staging-2026-04-15T00-35-00-000Z" \ --tags "repo:my-app,owner:Platform,type:buy,env:staging,source:mcp" \ -e staging \ --note "canary v42" \ -o /abs/project/load-test-results/buy-staging-2026-04-15T00-35-00-000Z.json \ /abs/project/tests/load/buy.yml

Optional fields:

  • tagTemplates — {flow}, {env}, plus any caller-supplied templateVars (e.g. {round})
  • outputDir — relative to project root; if missing, outputs land at project root
  • defaultTags — merged before templates
  • environments — if empty, any environment name is accepted

Override on the call side: name, note, extraTags, outputJson, reportHtml, variables, overrides, record: false, validateOnly, extraArgs, templateVars.

Optional feature #2 — Counter-group bucketing (counterBreakdown)

When you emit custom counters via events.emit('counter', 'shop.step.add_item.happy', 1), Artillery aggregates them into aggregate.counters. This server returns ALL of them in allCounters. Add counterGroups to your config to also get a pre-bucketed counterBreakdown in parse_results and read_artillery_output responses — ideal for CI pass/fail views and semantic grouping.

Config:

{

"counterGroups": { "name": "shopBreakdown", "prefix": "shop.", "buckets": [ { "key": "steps", "match": "^shop\\.step\\." }, { "key": "cart", "match": "^shop\\.cart\\." }, { "key": "payment", "match": "^shop\\.payment\\." }, { "key": "flow", "match": "^shop\\.flow\\." }, { "key": "other", "default": true } ] } }

Example response (`parse_results`):

{

"summary": { "requestsTotal": 1500, "rpsAvg": 25, "latencyMs": { "p95": 850 }, "errors": {} }, "allCounters": { "shop.step.add_item.happy": 90, "http.requests": 1500, /* ... */ }, "allRates": { "http.request_rate": 25 }, "allSummaries": { "http.response_time": { "min": 45, "p99": 1800 } }, "counterBreakdown": { "steps": { "shop.step.add_item.happy": 90, "shop.step.add_item.fail": 2 }, "cart": { "shop.cart.failure.quantity_update": 1 }, "payment": {}, "flow": { "shop.flow.started": 100 }, "other": {} } }

Rules:

  • prefix (optional) — counters not starting with this string are ignored
  • buckets — ordered; first match wins
  • One bucket may have default: true — catches everything that didn't match
  • Invalid regex → throws at parse time (fix your config)

Without counterGroups, the counterBreakdown field is simply absent from responses.

Full config reference

{

"flows": { " ": " " }, // enables run_project_lt "environments": [" ", "..."], // optional whitelist "defaultTags": { " ": " " }, "tagTemplates": ["type:{flow}", "env:{env}"], "outputDir": "load-test-results", "counterGroups": { // enables counterBreakdown "name": "<output

Only the beginning is shown; read the rest in the repo