Agents Index

Loadster

Online

Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.

Visit publisherConnectJSON

What it can do: 62 tools

  • get_screenshot read-onlyFetch a screenshot captured during a play as a viewable image. Use the screenshotKey from a step in get_play_status.
  • get_command_schema read-onlyGet the recursive schema for one command type, so you can build a valid command object. Some fields carry a 'notes' string describing accepted keys that aren't reflectable, such as element action options and locator attr
  • get_example read-onlyGet a small, valid worked example script for a bot type to use as a starting point.
  • get_scripting_api read-onlyList the scripting API scopes (bot, http, browser, ...) available in code blocks, or fetch one scope's members with their signatures and docs.
  • get_variable_schema read-onlyGet the schema for binding a script variable to a dataset, including the accepted update and selection strategies. A variable is a named row cursor bound to one whole dataset by dataSetId: on each pull it holds an entire
  • list_command_types read-onlyList the command (step) types available for a bot type, with a description and the bot types each applies to. Use this before authoring commands.
  • validate_script read-onlyStructurally validate a list of commands for a bot type before saving or playing, reporting any issues by command index. Pass the script's variables as well and it also cross-checks the bindings against the ${...} and bo
  • append_dataset_rowsAdd rows to the end of an existing dataset, sending only the new rows — the rows already in the table stay as they are, so there is no need to read them first. Every row must have as many columns as the table already has
  • create_datasetCreate a new dataset in a project. Loadster treats every row as data and addresses columns by zero-based index — a header row would be fed to bots like any other row, so don't add one when authoring values. Unless the us
  • delete_datasetDelete a dataset from a project.
  • get_dataset read-onlyGet a single dataset's shape — name, row and column counts, tag names, dashboard link — plus a leading window of its rows: the first five in table order by default, more with offset and limit. Compare rowOffset and the r
  • list_datasets read-onlyList the datasets in a project with their id, name, row/column counts, and tag names (without the full value table). Tags are shared across the team: to tag an item, reuse a name the list tools already report, and create
  • update_datasetUpdate an existing dataset. Each of name, values, and tags is optional: a field left out keeps its stored value, so a rename leaves the table alone. Values sent become the entire table, so send the complete table includi
  • list_engines read-onlyList everywhere a population can run, with the customer's own limits a scenario is written against. Each entry's id is what a population's engineId names — never invent one. Type CLOUD is a single Loadster cloud region,
  • submit_feedbackOptional. Sends a note about this tool surface to the Loadster team, who read it to fix what the surface got wrong. Nothing requires it and no task depends on it. A note is about the tools themselves: what worked, what w
  • get_documentation read-onlyList the Loadster manual's topics with their keys and URLs, or read up to 3 topics' text by key. Pass one key as topic, or up to 3 keys as topics. Omit both to list every topic.
  • create_monitorCreate a Monitor in a project, initially disabled. An enabled Monitor runs on its schedule, unattended. Its Cycles burn Fuel unless the account has a plan that includes monitoring, which covers them up to its limits. Ena
  • delete_monitorDelete a Monitor from a project. Its Incidents are deleted with it and it is removed from any status pages; the Script it played is left alone. To stop a Monitor running without losing it, use disable_monitor instead, wh
  • disable_monitorDisable a Monitor, stopping its scheduled Cycles and the Fuel or plan usage they bring; disabling closes the Monitor's open Incidents. Idempotent. Disabling, and enabling again with enable_monitor, both need the "Launch"
  • enable_monitorEnable a disabled Monitor so its Cycles run on its schedule. Enabling starts a Cycle at once, and the result's startedCycleId names it; startedCycleId is absent when no Cycle started, because the Monitor was already enab
  • get_incident read-onlyGet a single Incident: when it opened and closed, every notification that went out with its delivery outcome, the status events recorded on it, and the ids of the Cycles that opened and closed it. To reconstruct what hap
  • get_monitor read-onlyGet a single Monitor's full configuration and dashboard link. Configuration only — a Monitor's steps are its Script's commands, so read them with get_script. To start a disabled Monitor, call enable_monitor at the "Launc
  • get_monitor_cycle_detail read-onlyGet one Cycle in full: status, failure message, the engine it ran from, timestamps, and every metric the Monitor's thresholds judge. Its scriptRunId is a played run like any other — pass it with the project id to get_pla
  • get_monitoring_summary read-onlyGet the Monitoring Summary for a project: the aggregate health picture across its Monitors over a period, defaulting to the last 7 days, with per-Monitor and per-day aggregates for trends (times in seconds; performance s
  • list_incidents read-onlyList a project's Incidents — open ones first, then the most recently closed; unresolved only by default, with includeResolved for incident archaeology over a since/until window and monitorId to ask about one Monitor. An
  • list_monitor_cycles read-onlyList a Monitor's Cycles, newest first — one row per Cycle with its status, timestamps, the engine id it ran from, and headline response times; a Cycle with no status yet is scheduled or still running. Window with since/u
  • list_monitoring_locations read-onlyList everywhere a Monitor's Cycles can run from. Each entry's id is what a Monitor's engineIds names — never invent one. Type CLOUD is one of Loadster's shared monitoring locations, and PRIVATE is one of the customer's o
  • list_monitors read-onlyList the Monitors in a project. A Monitor is a scheduled, low-volume check that runs a Script on a frequency to verify health and alert on failure; each execution is a Cycle. Each row is a summary without the thresholds
  • update_monitorUpdate an existing Monitor's exposed configuration: name, Script, frequency, engine ids, failure and recovery thresholds, tags, and the acceptable-metric thresholds. Each is optional: a field left out keeps its stored va
  • get_load_test_report read-onlyGet a finished Load Test's Test Report — aggregate totals, the error and advice picture behind the Dashboard's advice tile, per-Population outcomes, and each engine's average and peak CPU; an unfinished test answers with
  • get_load_test_status read-onlyGet a Load Test's live status, as the Dashboard's live test view shows it: stage, elapsed time, Bots started, running, peak and planned per Population, Iterations, response time percentiles, throughput, errors by type, a
  • get_load_test_url_timings read-onlyGet a finished Load Test's response times per URL, slowest first by the total time all hits to the URL took: hits, average, minimum and maximum response time, and average time to first byte, in milliseconds. Use it to na
  • list_load_tests read-onlyList a project's Load Tests, a window of summary rows at a time: the ones in progress first, each with its stage, then the finished ones, newest first. A Load Test is a run of a Scenario at scale by many bots; launch_loa
  • stop_load_testStop a Load Test. By default the stop is graceful, as the Dashboard's Stop button does: each bot finishes the iteration it is on before it stops, so the last iterations complete and are reported in full. With immediate s
  • update_load_test_notesReplace the notes on a finished Load Test's Test Report — the only thing on a Load Test this surface edits. Ask the user before writing: notes belong to the user, and advising on a test never requires writing them. The t
  • create_scenarioCreate a scenario in a project — saving costs nothing and starts nothing. Launch it with launch_load_test at the "Launch" access level; below that level a call is refused, and the user launches it from the Dashboard at t
  • delete_scenarioDelete a scenario from a project. The scripts its populations referenced are left alone.
  • get_scenario read-onlyGet a single scenario including its Populations, plus a dashboard link and its launch readiness: the account's fuelBalance; launchBlockers, where an empty list means it can launch as it stands; and estimatedFuelLow and e
  • launch_load_testLaunch a saved Scenario as a Load Test, exactly as stored. Its Populations send real traffic to the user's site. Like the Dashboard's Launch button, it runs on the account's plan when get_scenario shows no Fuel estimate
  • list_scenarios read-onlyList the scenarios in a project with their id, name, version, population count, peak bots, total duration in milliseconds, and tag names — without the populations, fuel estimate, and launch blockers get_scenario reports.

…and 22 more.

Connect it

Claude Code
claude mcp add --transport http loadster https://api.loadster.com/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.loadster.com/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "loadster": {
      "url": "https://api.loadster.com/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "loadster": {
      "type": "http",
      "url": "https://api.loadster.com/mcp"
    }
  }
}

Questions

What does Loadster do?

Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots. It exposes 62 tools to AI assistants.

What tools does Loadster provide?

62 tools, including get_screenshot, get_command_schema, get_example, get_scripting_api, get_variable_schema, list_command_types, validate_script, append_dataset_rows, create_dataset, delete_dataset, get_dataset, list_datasets….

How do I connect Loadster to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.loadster.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Loadster require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Loadster online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Loadster?

loadster.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Cloud & DevOps