About this integration
MCP server for Artillery 2.x — full flags, Fargate, raw-text parser, project launcher (MIT)
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.7
- Package
- @kosiakmd/artillery-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@kosiakmd/artillery-mcpPublisher documentation and manifest were reviewed; neither the package nor Artillery/AWS/cloud operations were executed or independently security-audited. Several tools can run load tests or cloud jobs and therefore require operator-scoped permissions and targets.
Capabilities: Run local Artillery tests, Parse and compare Artillery results, Launch documented Fargate test runs, Manage saved test configurations
Connected profiles
Additional details
io.github.kosiakMD/artillery-mcp
Source ↗ · Checked 2026-09-170.1.7
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@kosiakmd/artillery-mcp
Source ↗ · Checked 2026-09-190.1.7
Source ↗ · Checked 2026-09-19Publisher documents a zero-config stdio MCP server that an MCP client launches with npx.
Source ↗ · Checked 2026-09-19Local operations do not require a credential; Artillery Cloud recording uses the documented ARTILLERY_CLOUD_API_KEY, so the listing records API-key authentication for that capability.
Source ↗ · Checked 2026-09-19The reviewed npm package is launched with npx over stdio and may receive working-directory and cloud-key environment variables.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19