Locust MCP Server

Related Servers

Alternatives to Locust MCP Server

No user-submitted related servers found.

Related Servers

JMeter MCP Server
Testing & QA Tools Command Line Autonomous Agents
QAInsights
F
license
B
quality
D
maintenance
A Model Context Protocol server that allows AI assistants to execute and manage JMeter performance tests through natural language commands.
Updated 16 days ago (2026-09-12 16:04 UTC)
6
73
-
k6-mcp-server
Testing & QA Tools Code Execution Monitoring
QAInsights
A
license
C
quality
D
maintenance
A Model Context Protocol (MCP) server implementation that allows AI assistants to run k6 load tests through natural language commands, supporting custom test durations and virtual users.
Updated a year ago (2025-04-06 23:40 UTC)
2
26
MIT
k6 MCP Server
Testing & QA Tools Monitoring
dil-anoojibettu
F
license
Not graded
quality
D
maintenance
Enables running k6 load tests with customizable duration and virtual users via natural language, with real-time output and LLM-powered analysis.
Updated a year ago (2025-08-06 07:35 UTC)
1
-
MCP-Midscene
Testing & QA Tools App Automation Browser Automation
MauroCor
F
license
A
quality
D
maintenance
A server that allows using natural language to automate test flows with Playwright, leveraging MidScene's AI agent capabilities to interact with web elements and perform assertions.
Updated a year ago (2025-06-19 01:38 UTC)
12
-
LogAnalyzer MCP Server
Monitoring Observability Developer Tools
ChiragPatankar
A
license
B
quality
C
maintenance
An AI-powered server that provides rapid debugging of server logs with actionable fixes in under 30 seconds, featuring real-time monitoring and root cause analysis through Google Gemini integration.
Updated 3 months ago (2026-07-06 09:10 UTC)
7
4 npm
MIT
Testing MCP
Testing & QA Tools Code Analysis
shalonjovan
A
license
Not graded
quality
D
maintenance
A universal AI-powered testing server built on the Model Context Protocol (MCP). Allows AI agents to inspect, execute, test, monitor, debug, and report on software projects.
Updated 3 months ago (2026-07-09 05:11 UTC)
3
GNU Lesser General Public v2.1 only

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.7/5.0

Scored 2026-04-18 10:45 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'run_locust' has a clear and distinct purpose that cannot be mistaken for any other tool in this set.

Naming Consistency5/5

The single tool name 'run_locust' follows a clear verb_noun pattern, and with only one tool, there is perfect consistency. There are no other tools to compare against, so no inconsistencies can exist.

Tool Count2/5

A single tool is too few for most server purposes, as it severely limits functionality and flexibility. For a Locust server, one might expect additional tools for tasks like configuring tests, viewing results, or managing load scenarios, making this set feel incomplete and under-scoped.

Completeness1/5

The tool set is severely incomplete for a Locust server, which typically involves multiple aspects of load testing such as setup, execution, monitoring, and analysis. With only a 'run' tool, there are significant gaps that will cause agent failures, as it lacks coverage for configuration management, result retrieval, or test lifecycle operations.