About Stresix
Stresix is a hosted MCP server for load testing an app before launch, aimed at developers using agents or MCP clients. It builds a GitHub repository or Docker image, runs simulated users against it in a private network, and returns latency, errors, bottlenecks, and a server-size recommendation.
Key features
- 01Build from GitHub or Docker image
- 02Run simulated-user load tests
- 03Track live test status and metrics
- 04Report bottlenecks and server sizing
- 05Require confirmation for paid runs
Use cases
- 01Check app capacity before launch
- 02Measure latency and error rates
- 03Find resource bottlenecks under load
- 04Estimate an appropriate server size
MCP support
Exposes tools to start load tests, check run status, and retrieve reports through hosted Streamable HTTP. Tests target only the app Stresix builds on its own server.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://stresix.com/mcpclaude mcp add --transport http com-stresix-stresix https://stresix.com/mcp{"mcpServers":{"com-stresix-stresix":{"type":"http","url":"https://stresix.com/mcp"}}}Open in Cursor{"servers":{"com-stresix-stresix":{"type":"http","url":"https://stresix.com/mcp"}}}Open in VS Code{"mcpServers":{"com-stresix-stresix":{"type":"http","url":"https://stresix.com/mcp"}}}{"mcpServers":{"com-stresix-stresix":{"serverUrl":"https://stresix.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://stresix.com/mcpAuth requiredTools
14| Parameter | Type | Required | Description |
|---|---|---|---|
| env | object | No | Environment variables the app needs to boot, such as NODE_ENV or a test database URL. Stored encrypted and wiped after the run. Never send production secrets. |
| port | integer | No | The port the app listens on inside its container. Read it from the code or use inspect_target. Stresix tries 80, 3000, 5000, 8000 and 8080 when it is left out. |
| tier | enum | No | Run size. Leave it out to use the free Lite run when available.lite | standard | massive |
| paths | array | No | GET paths the simulated users rotate through, for example ["/", "/api/products", "/search?q=shoes"]. Pick pages that hit the database. Defaults to ["/"]. Use requests instead for other methods, headers or bodies. |
| branch | string | No | Repository branch to build. The default branch when left out. |
| target | string | Yes | GitHub repository URL (https://github.com/owner/repo) or a Docker image (nginx:1.27, ghcr.io/owner/app:tag). |
| requests | array | No | Full requests the simulated users rotate through, in place of paths. Each one is independent (no multi-step flows). Headers such as Authorization are stored encrypted and wiped after the run. Use a test account token, never a production secret. {{vu}} (the simulated user's number) and {{iteration}} (that user's request count) can go in a path, header value or body and are filled in per request, for example to give each user its own id. |
| confirm_spend | boolean | No | Set to true only after the user agreed to spend credits on this run. |
| current_server | object | No | The server the user runs the app on today, if any. The report then says whether that server is enough instead of recommending a size. Can also be set after the run with set_current_server. |
| current_server.vcpu | number | Yes | |
| current_server.label | string | No | A name for it, like "Hetzner CX22" or "DigitalOcean 2 GB droplet". |
| current_server.ram_gb | number | Yes |
Details
From the project READMEStresix MCP server
Load test your app from Claude Code, Cursor or any MCP client before you launch.
Tell your agent "load test this app before I launch". Stresix builds your GitHub repo or Docker image on a fresh cloud server, ramps simulated users at it from a second server in the same datacenter, and hands the report back to the agent: what ran out first, p95 latency, error rate and what server size to run it on. No k6 script to write.
The server is hosted at https://stresix.com/mcp (MCP over Streamable HTTP). Nothing to install.
Setup
- Sign in at stresix.com with GitHub, Google or email.
- Open Settings, then Keys for agents, and create a key. It is shown once.
- Add the server to your client.
Claude Code
claude mcp add --transport http stresix https://stresix.com/mcp \
--header "Authorization: Bearer YOUR_STRESIX_KEY"
Cursor (~/.cursor/mcp.json, or .cursor/mcp.json in a project)
{
"mcpServers": {
"stresix": {
"url": "https://stresix.com/mcp",
"headers": { "Authorization": "Bearer YOUR_STRESIX_KEY" }
}
}
}
Windsurf (~/.codeium/windsurf/mcp_config.json)
{
"mcpServers": {
"stresix": {
"serverUrl": "https://stresix.com/mcp",
"headers": { "Authorization": "Bearer YOUR_STRESIX_KEY" }
}
}
}
VS Code (.vscode/mcp.json)
{
"servers": {
"stresix": {
"type": "http",
"url": "https://stresix.com/mcp",
"headers": { "Authorization": "Bearer YOUR_STRESIX_KEY" }
}
}
}
Tools
| Tool | What it does |
|---|---|
start_load_test | Builds and load tests a GitHub repo URL or Docker image. Takes the port, up to 10 GET paths, a branch, env vars the app needs to boot and the run size. |
get_test_status | Building, starting servers, or running with live users, requests per second, p95 and error rate. |
get_test_report | The verdict when the run is done: users held, p95, error rate, what ran out first, what to change and the server size to pick. |
Pricing
| Run | Load | Target server | Cost |
|---|---|---|---|
| Lite | 500 users, 4 minutes | 2 vCPU / 4 GB | Free once per person |
| Standard | 2,500 users, 10 minutes | 4 vCPU / 8 GB | 1 credit |
| Massive | 10,000 users, 15 minutes | 8 vCPU / 16 GB | 3 credits |
Credits come in packs: $10 for 5, $40 for 25.
Safety
- A paid run never starts on its own. The tool answers with the price and your balance first, and the agent has to ask you before calling it again with
confirm_spend: true. - With no credits left, the tool says to top up at stresix.com and starts nothing.
- Each key can start 4 runs an hour, on top of the account's daily limit, so an agent stuck in a loop cannot spend a balance.
- Load only ever goes to the app Stresix builds, on its own server in a private network. It cannot be pointed at a live site.
- A key can start runs and read their status and reports. It cannot buy credits or change the account. Revoke it in Settings and it stops working at once. Only a hash of each key is stored.
Example
You: load test this app before I launch, I'm on a 2 vCPU box
Agent: reads the code, finds the app listens on 3000 and that
/,/api/productsand/searchhit the database, then callsstart_load_testwith the repo URLStresix: Started a Lite run (500 users for 4 minutes against 2 vCPU / 4 GB). This is the free run, nothing was charged.
Agent: polls
get_test_status, then callsget_test_reportand summarizes what ran out first and what to change.
More at stresix.com/mcp.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.