Can my agent start a Gatling simulation run via chat?

Yes. Use the 'start_simulation' tool with the specific Simulation ID. The agent will command the Gatling Enterprise infrastructure to begin the load test and return a unique run ID for tracking.

How do I check the request statistics for a completed test run via chat?

Use the 'get_run' tool. Provide the Run ID. Your agent will fetch the full details of the execution, including request stats, error counts, and the virtual user peak reached during the test.

Can I see my credit quotas and team member counts through the agent?

Absolutely. Use the 'list_teams' tool. Your agent will enumerate the teams registered in your Gatling Enterprise account and monitor their member counts and available credit quotas natively.

Gatling MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Gatling
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Gatling and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Gatling MCP Server

Connect your Gatling Enterprise account to any AI agent and take full control of your performance testing and high-scale load simulation through natural conversation.

GitHub Copilot Agent mode brings Gatling data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Simulation Orchestration — List all Gatling simulations defining load scenarios and retrieve IDs, class names, and team associations natively
Live Test Execution — Trigger new performance test runs on Gatling Enterprise infrastructure and retrieve unique run IDs flawlessly
Test Run Monitoring — Track execution progress, statuses, and peak virtual user (VU) counts for ongoing or completed simulations synchronously
Detailed Stats Retrieval — Access full run details including request statistics, error counts, and injection start/end times limitlessly
Team & Quota Oversight — Enumerate teams registered in Gatling Enterprise and monitor member counts and credit quotas securely
Artifact Management — List uploaded test packages and artifacts to verify versions and upload timestamps across your environment
Resource Pool Auditing — Retrieve the list of load generator pools, identifying regions and instance counts to verify scaling capacity
Autonomous Aborting — Stop all load generators for a running simulation immediately to manage system resources and prevent overruns

The Gatling MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Gatling to VS Code Copilot via MCP

Follow these steps to integrate the Gatling MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Gatling

Ask Copilot: "Using Gatling, help me...". 10 tools available

Why Use VS Code Copilot with the Gatling MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Gatling through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Gatling + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Gatling MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Gatling MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Gatling to VS Code Copilot via MCP:

abort_simulation

Abort a running Gatling simulation

get_run

Get full details of a Gatling run

get_simulation

Get full details of a Gatling simulation

list_packages

List uploaded packages/artifacts on Gatling Enterprise

list_pools

List load generator pools on Gatling Enterprise

list_runs

List runs for a Gatling simulation

list_simulations

Simulations define load scenarios with VU populations. Returns names, IDs, class names, and team associations. List all simulations on Gatling Enterprise

list_teams

List teams on Gatling Enterprise

list_tokens

List API tokens on Gatling Enterprise

start_simulation

Returns run ID. Start a Gatling simulation run

Example Prompts for Gatling in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Gatling immediately.

"List all simulations on Gatling Enterprise"

"Start simulation 'abc-123'"

"Show me the stats for run 'run_xyz789'"

Troubleshooting Gatling MCP Server with VS Code Copilot

Common issues when connecting Gatling to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Gatling + VS Code Copilot FAQ

Common questions about integrating Gatling MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.