Enterprise DNA
M MCP Servers Developer low

qainsights/locust-mcp-server

by Various

A Model Context Protocol (MCP) server implementation for running Locust load tests. This server enables seamless integration of Locust load testing capabilities with AI-powered dev

Q

MCP

qainsights/locust-mcp-server

Added 1 June 2026

#locust #mcp #mcp-server #model-context-protocol #performance-testing

Overview

An MCP server that lets you run Locust load tests from AI coding assistants. It wraps Locust's distributed load testing engine behind the Model Context Protocol so tools like Claude can start, monitor, and stop tests programmatically.

Best for

Best for
Developers who want to kick off Locust tests from an AI assistant without switching tools

Use cases

  • Trigger a load test from a chat prompt during code review
  • Check test results and failure rates without leaving the IDE
  • Automate performance regression checks in a CI pipeline

Notes

An MCP server that lets you run Locust load tests from AI coding assistants. It wraps Locust’s distributed load testing engine behind the Model Context Protocol so tools like Claude can start, monitor, and stop tests programmatically.

12 stars on GitHub. Last updated 2025-04-06. Licensed MIT.

Use cases

  • Trigger a load test from a chat prompt during code review
  • Check test results and failure rates without leaving the IDE
  • Automate performance regression checks in a CI pipeline

Pros

  • Brings load testing into conversational workflows
  • Lightweight Python implementation with few dependencies
  • Open source with a clear, focused scope

Cons

  • Very early stage with only 12 GitHub stars
  • Limited documentation and community support
  • Requires a running Locust environment to be useful

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Brings load testing into conversational workflows
  • Lightweight Python implementation with few dependencies
  • Open source with a clear, focused scope

Cons

  • Very early stage with only 12 GitHub stars
  • Limited documentation and community support
  • Requires a running Locust environment to be useful