Loadster MCP

Loadster is a cloud load testing and monitoring platform. Its built-in Model Context Protocol (MCP) server lets AI agents like Claude, ChatGPT, Codex, Cursor, and VS Code write and play load test scripts, build load test scenarios, set up monitors, and analyze results in your Loadster account.

This repository is the public home for connecting to that server: setup snippets for each client, the Claude Code plugin, and the metadata behind Loadster's listings in MCP directories. The server itself is hosted by Loadster at https://api.loadster.com/mcp, and its source is not published here. Loadster is also an official plugin in the ChatGPT and Codex plugin directory.

The maintained, full-length guide is the AI Assistants & MCP chapter of the Loadster manual. This README is the short version.

The Loadster MCP endpoint

A client can connect and read the tool list without signing in, so it can show what Loadster offers before you have an account. Using any tool needs OAuth or a personal access token, and some clients ask you to sign in as soon as you add the server.

OAuth is the easiest way to connect. Clients that support MCP OAuth send you to Loadster to approve the connection in your browser, and you can review or revoke connected agents on the API & MCP page in your Loadster settings. The approval page leads with the web address Loadster can verify for the app, so check that it's one you expect before you approve. You also choose an access level there: Read (selected to start with), Edit, or Launch. To change it later, revoke the connection and connect again. Changing or resetting your Loadster password disconnects every OAuth-connected agent, so reconnect each one afterward. Personal access tokens keep working.

Personal access tokens are for clients that can't do OAuth, and for CI jobs and scripted agents. The same kind of token also works for calling the Loadster REST API directly. Create one in the Loadster dashboard under Settings → API & MCP → Personal Access Tokens, choose its access level, copy it right away (it's only shown once), and send it as Authorization: Bearer YOUR_TOKEN. A token acts as you within the team where you created it, so treat it like a password.

Connecting Claude Code to Loadster

The quickest way is the plugin from this repository, which adds the Loadster MCP server plus skills for a sensible load testing workflow: setup to connect, setup-script for a first script, setup-scenario for a first load test scenario, setup-monitor for a first synthetic monitor, load-test for a full test, and results for reading what happened.

/plugin marketplace add loadster/loadster-mcp
/plugin install loadster@loadster

Then run /mcp, pick loadster, and approve the OAuth connection in your browser. Ask Claude something like "List my Loadster projects" to confirm it can reach your account.

Without the plugin, add the server directly and Claude Code will walk you through OAuth:

claude mcp add --transport http loadster https://api.loadster.com/mcp

Or with a personal access token, for headless use:

claude mcp add --transport http loadster https://api.loadster.com/mcp --header "Authorization: Bearer YOUR_TOKEN"

The equivalent project-level .mcp.json:

{
  "mcpServers": {
    "loadster": {
      "type": "http",
      "url": "https://api.loadster.com/mcp"
    }
  }
}

Connecting Claude Desktop and claude.ai to Loadster

Claude Desktop and c

... View full README on GitHub