How to Use the Gatling MCP in Cursor

Q: Can Cursor help me debug a failed Gatling run?

Yes, Cursor uses getrun to pull the execution metrics and error logs. The agent then analyzes these statistics alongside your local code to find the bottleneck. This helps you identify performance regressions immediately.

Q: How does Cursor handle Gatling load generator pools?

The agent uses listpools to check which generators are available before starting a test. Cursor displays this information so you don't waste time trying to run tests on offline infrastructure.

Write load-testing scripts and run Gatling simulations directly inside Cursor to verify performance as you write code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Gatling MCP to Cursor

Create your Vinkius account to connect Gatling to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Gatling with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Trigger Gatling runs inside the Cursor editor

The `start_simulation` tool initiates load tests on Gatling Enterprise, while `list_runs` retrieves previous execution history. Cursor uses these tools to run simulations right next to your active code branch. You get instant feedback on whether your latest commit broke your response time budget. This MCP Server lets your agent check performance metrics without breaking your focus. If a test fails, Cursor scans the run history to pinpoint when the slowdown started. You fix the performance bug before you even push to staging.

Match Cursor code with Gatling packages

The `list_packages` tool fetches uploaded artifacts, and `get_simulation` retrieves the specific class configuration for your Gatling scenarios. Cursor cross-references these details with your local Scala or Java load-testing scripts. This ensures the code you are editing matches the package deployed on your load generators. Your agent analyzes these configurations to prevent version mismatches. If you edit a simulation locally, Cursor checks if you need to upload a new package first. It keeps your local workspace in sync with your cloud testing environment.

Inspect Gatling pools and tokens with this MCP Server

The `list_pools` tool displays available load generator pools, and `list_tokens` checks your active API keys. Cursor queries these tools to verify your development environment is authorized and has the capacity to run a test. You avoid failed runs caused by exhausted generator pools or expired credentials. Having these tools in your editor keeps your deployment pipeline clean. Cursor alerts you if a generator pool is down before you queue a massive load test. It saves you from waiting on a test that was doomed to fail from the start.

Setup guide

Set up Gatling MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Gatling MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Gatling transactions." If the MCP tools are loaded correctly, Cursor will call the Gatling tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "gatling-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Gatling. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Gatling now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Gatling MCP in Cursor

You ask the Cursor agent to start a test run. The agent calls `start_simulation` with your target simulation ID and returns the run details. You see the test progress directly in your editor's chat panel.

Yes, Cursor uses `get_run` to pull the execution metrics and error logs. The agent then analyzes these statistics alongside your local code to find the bottleneck. This helps you identify performance regressions immediately.

The agent uses `list_pools` to check which generators are available before starting a test. Cursor displays this information so you don't waste time trying to run tests on offline infrastructure.

Yes, you can abort any running simulation. Ask your agent to stop the test, and it executes `abort_simulation` to terminate the active run. This stops the generators immediately to prevent runaway cloud costs.

Absolutely, because all requests go through the secure Vinkius gateway. Cursor only receives the JSON responses from `list_packages` and `get_run` via an encrypted local channel. Your actual simulation binaries and load test payloads are never processed or stored by third parties.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript