convez.ai
MCP ServerDevOps & InfraestruturaIntermediário
kosiakMD

Artillery MCP Plugin

kosiakMD/artillery-mcp-plugin

Testes de carga Artillery integrados ao Claude Code via MCP

Ver no GitHub
InicialPluginScore · de 0 a 100

Plugin Claude Code que integra testes de carga com Artillery 2.x via MCP em um único comando. Fornece 18 ferramentas para executar testes HTTP, analisar resultados e comparar baselines sem configuração manual. Suporta opcionalmente fluxos de projeto nomeados e ambientes múltiplos via arquivo de configuração.

Instalação

$npx convez-ai kosiakMD/artillery-mcp-plugin

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 7 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Executar testes de carga rápidos contra APIs e serviços web
  • Analisar métricas de latência (p50, p95, p99) em resultados JSON
  • Comparar resultados de testes e detectar regressões de performance
  • Orquestrar testes em múltiplos ambientes (local, staging, prod)
  • Registrar e rastrear execuções no Artillery Cloud

Veredito

Excelente para engenheiros de performance e DevOps que usam Claude Code. A integração via MCP elimina configuração manual e o conjunto de 18 ferramentas cobre workflows comuns de teste de carga. Requer Artillery CLI pré-instalado no host (ou Docker alternativo).

README

A tradução para o português deste README ainda está na fila.

artillery-mcp-plugin

Claude Code plugin for @kosiakmd/artillery-mcp — Artillery 2.x load-testing via MCP. Installs the MCP server + agent skill in one command, no manual claude mcp add.

What's in the box

  • MCP server: @kosiakmd/artillery-mcp (stdio, via npx — no global install required)
  • Agent skill: SKILL.md with decision tree / tool call patterns / common gotchas, auto-loaded by Claude Code when the plugin is enabled

Install

In a Claude Code session:

/plugin marketplace add kosiakMD/artillery-mcp-plugin
/plugin install artillery-mcp@artillery-mcp

Restart your session. You now have 18 MCP tools (19 if the target project has .artillery-mcp.config.json for the opt-in project launcher).

Prerequisites

  • Artillery CLI on PATH — npm install -g artillery@latest. The MCP wraps it; the npm package doesn't bundle the binary.
  • Node.js ≥ 20
  • ARTILLERY_CLOUD_API_KEY — only if you want to record runs to Artillery Cloud. Export it in your shell before launching Claude Code, or load via a dotenv wrapper; see the MCP README § Security.

Prefer Docker (no host Node/Artillery)? Skip this plugin — use the Docker variant directly as documented in the MCP README § Docker.

What you can do after install

You: "Run a quick HTTP test against https://api.example.com at 50 req/s for 30 seconds"
Claude: [calls mcp__artillery-mcp__quick_test → returns summary]

You: "Parse results.json and show me the latency breakdown"
Claude: [calls mcp__artillery-mcp__parse_results → formatted p50/p95/p99]

You: "Compare baseline.json vs yesterday.json — did anything regress?"
Claude: [calls mcp__artillery-mcp__compare_results → diff with thresholds]

Full tool reference: MCP README § tools.

Optional — project launcher

If your project uses multiple named flows (e.g. free, paid, combined for different checkout variants), add .artillery-mcp.config.json at the repo root:

{
  "flows": { "smoke": "tests/load/smoke.yml" },
  "environments": ["local", "staging", "prod"],
  "defaultTags": { "repo": "my-app" },
  "tagTemplates": ["type:{flow}", "env:{env}"],
  "outputDir": "load-test-results"
}

Then run_project_lt appears as a 19th tool:

You: "Run smoke on staging, note 'canary v42'"
Claude: [calls run_project_lt(flow="smoke", environment="staging", note="canary v42")]

Full config schema: MCP README § Full config reference. To scaffold: npx @kosiakmd/artillery-mcp init in your project.

Versioning

ComponentVersionWhere pinned
Plugin0.1.0.claude-plugin/marketplace.json + plugins/artillery-mcp/.claude-plugin/plugin.json
MCP server^0.1 (resolves to latest 0.1.x)plugins/artillery-mcp/.claude-plugin/plugin.json → mcpServers.artillery-mcp.args

Plugin bumps happen for skill content / manifest changes. MCP bumps are independent and auto-picked via caret-minor.

See also

License

MIT. See LICENSE.

Ver o original no GitHub

Bom para

Relacionados