MCP server update

Every resource, not just the read-only ones

The Gatling MCP Server is a local server that exposes your Gatling Enterprise Edition account to Claude Code, Cursor, Windsurf, or any MCP-compatible client. Your agent now reads and writes across your entire test lifecycle. It can register source repositories, create and start runs, and pull each run's logs and performance reports directly into your conversation.

• Teams: List all teams visible to the API token
• ‍Packages: List managed and private packages
• ‍Source repositories: List, view, register, or delete git repositories a test can build from
• ‍Locations: List managed and private load generator locations
• ‍Tests: List, view, create, update, delete, and start tests
• ‍Runs: List, view, get status, read logs, read per-request/per-group reports, share a public link, update, and stop runs

Every tool declares its own required role: Read, Configure, or Start. Scope your API token to exactly what you want the agent doing.

From "what do I have" to "make it happen"

Your agent pulls real team IDs, location names, and package and repository references live from your account, right when it needs them to register a repo, configure a test, or launch a run.

That same context carries into diagnosis. When a run fails, your agent cross-references the execution logs against the performance report and tells you whether it was a build error, an injection crash, or a stop criteria breach. When a run succeeds, it can read straight into the per-request data to answer questions like "what's the p95 for the login request?"

Drop it into the client you already use

Available as an NPM package and a Docker image. Compatible with Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, and any client that supports the Model Context Protocol.

‍

*Requires: Gatling Enterprise Edition account · API token scoped to Read, Configure, or Start · Node.js 20+ or Docker