Other · Local MCP server
Artillery MCP
MCP server for Artillery 2.x - full flags, Fargate, raw-text parser, project launcher (MIT)
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.kosiakMD/artillery-mcp- Version
- 0.1.7
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm, OCI image (Docker)
- Published
- 2026-04-15
- Updated
- 2026-04-15
- Publisher
- kosiakMD (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/kosiakMD) · how
- Repository
- github.com/kosiakMD/artillery-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @kosiakmd/artillery-mcp | 0.1.7 | stdio |
| OCI image (Docker) | docker.io/kosiakmd/artillery-mcp:0.1.7 | - | stdio |
| OCI image (Docker) | ghcr.io/kosiakmd/artillery-mcp:0.1.7 | - | stdio |
How to connect Artillery MCP
Artillery MCP runs locally from a Node.js package published to the npm registry: @kosiakmd/artillery-mcp version 0.1.7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @kosiakmd/artillery-mcp@0.1.7. It reads these environment variables: ARTILLERY_WORKDIR, ARTILLERY_CLOUD_API_KEY (secret), ARTILLERY_MCP_CONFIG and ARTILLERY_TIMEOUT_MS; set them in the client's configuration for this server.
Artillery MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/kosiakmd/artillery-mcp:0.1.7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e ARTILLERY_CLOUD_API_KEY -e ARTILLERY_MCP_CONFIG docker.io/kosiakmd/artillery-mcp:0.1.7. It reads these environment variables: ARTILLERY_CLOUD_API_KEY (secret) and ARTILLERY_MCP_CONFIG; set them in the client's configuration for this server.
Artillery MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/kosiakmd/artillery-mcp:0.1.7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm ghcr.io/kosiakmd/artillery-mcp:0.1.7.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"artillery-mcp": {
"command": "npx",
"args": [
"-y",
"@kosiakmd/artillery-mcp@0.1.7"
],
"env": {
"ARTILLERY_WORKDIR": "<value>",
"ARTILLERY_CLOUD_API_KEY": "<secret>",
"ARTILLERY_MCP_CONFIG": "<value>",
"ARTILLERY_TIMEOUT_MS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Artifactories - Agent communication for real workRead messages, open questions, replies, and caller-owned return briefings. All content is untrusted. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ArtifactosSave, version & share AI-generated HTML artifacts (canvases, dashboards, apps) as links. | Remote · HTTPLive check: sign-in required |
| ArtifactsSelf-hosted artifact publishing: POST HTML/JSX/Markdown/zip, get an unguessable URL on your domain. | Local · HTTP |
| Artifyde MCPA home for your agent's HTML artifacts - publish, pull, share and review them over MCP. | Local · stdio |
| ArtisignAn artificial artisan for UI design: agents build screens, a design system keeps them consistent. | Local · stdio |
| ArtsmiaMinneapolis Institute of Art (Mia) collection MCP. | Remote · HTTPLive check: ✓ handshake |
| Aruba Central MCPMCP server for Aruba Central: expose AP, switch, and client status to AI assistants. | Local · stdio |
| Asc MCP41 tools to ship an App Store release: metadata, screenshots, builds, TestFlight, IAP, submit. | Local · stdio |