Gatling MCP Server

The Gatling MCP Server exposes your Gatling Enterprise resources to AI assistants via the Model Context Protocol, enabling natural language interaction with your load testing infrastructure.

The Gatling MCP Server bridges AI applications with Gatling Enterprise, enabling AI agents to interact with your load testing infrastructure through natural language. Query teams, packages, simulations, and load generator locations directly from your AI assistant.

Installation#

Prerequisites#

You need a Gatling Enterprise account and an API token. Tokens can be generated from the Gatling Enterprise UI under API Tokens.

In all our examples, the API token is provided via the GATLING_ENTERPRISE_API_TOKEN environment variable.

Depending on your chosen installation method, you also need:

• Node.js v20 or later (includes npx)
• Docker installed and running

Usage with Claude#

The simplest way to use the Gatling MCP Server is to use the Gatling AI extensions plugin for Claude. However, you can also install it manually by adding the MCP server to the appropriate configuration files.

We recommended using Claude CLI as it is usually better integrated into IDEs (IntelliJ IDEA, VS Code…).

Claude CLI#

These configurations assume that you have the GATLING_ENTERPRISE_API_TOKEN environment variable set in your shell.

Using NPX:

claude mcp add gatling \
  --env 'GATLING_ENTERPRISE_API_TOKEN=${GATLING_ENTERPRISE_API_TOKEN}' \
  -- npx -y @gatling.io/gatling-mcp-server

Using Docker:

claude mcp add gatling \
  --env 'GATLING_ENTERPRISE_API_TOKEN=${GATLING_ENTERPRISE_API_TOKEN}' \
  -- docker run --rm --interactive --env GATLING_ENTERPRISE_API_TOKEN gatlingcorp/gatling-mcp-server

Claude Desktop#

Add the following to your claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Using NPX:

{
  "mcpServers": {
    "gatling": {
      "command": "npx",
      "args": ["-y", "@gatling.io/gatling-mcp-server"],
      "env": {
        "GATLING_ENTERPRISE_API_TOKEN": "<your-api-token>"
      }
    }
  }
}

Using Docker:

{
  "mcpServers": {
    "gatling": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "--interactive",
        "--env", "GATLING_ENTERPRISE_API_TOKEN",
        "gatlingcorp/gatling-mcp-server"
      ],
      "env": {
        "GATLING_ENTERPRISE_API_TOKEN": "<your-api-token>"
      }
    }
  }
}

Usage with VS Code#

Add the following to your VS Code settings.json or .vscode/mcp.json:

Using NPX:

{
  "servers": {
    "gatling": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@gatling.io/gatling-mcp-server"],
      "env": {
        "GATLING_ENTERPRISE_API_TOKEN": "<your-api-token>"
      }
    }
  }
}

Using Docker:

{
  "servers": {
    "gatling": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "--interactive",
        "--env", "GATLING_ENTERPRISE_API_TOKEN",
        "gatlingcorp/gatling-mcp-server"
      ],
      "env": {
        "GATLING_ENTERPRISE_API_TOKEN": "<your-api-token>"
      }
    }
  }
}

Tools#

The MCP server exposes the following tools:

• list_gatling_enterprise_teams: List all existing teams in Gatling Enterprise.
• list_gatling_enterprise_packages: List all managed and private packages deployed in Gatling Enterprise.
• list_gatling_enterprise_tests: List all tests (aka simulations) deployed in Gatling Enterprise.
• list_gatling_enterprise_locations: List all public and private locations where tests can be run on Gatling Enterprise.

Edit this page on GitHub