Loadster
Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: test web applications.Similar tools
Listed for the same task: test web applicationsReviews
No review yet. Used Loadster? Be the first to help others choose.What it does
Loadster is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: browser automation. That makes it a candidate for tasks such as test web applications or book appointments online.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://api.loadster.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http loadster https://api.loadster.com/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"loadster": {
"url": "https://api.loadster.com/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Loadster answered an MCP connection on 15 Nov 2026 and introduced itself as loadster-mcp 2.2.1 (MCP protocol 2025-06-18).
62 tools offered to AI assistants
get_screenshot· Fetch a screenshot captured during a play as a viewable image. Use the screenshotKey from a step in get_play_status.get_command_schema· Get 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 attributes.get_example· Get a small, valid worked example script for a bot type to use as a starting point.get_scripting_api· List 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· Get 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 row, advancing perlist_command_types· List 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· Structurally 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 bot.getVariable readsappend_dataset_rows· Add 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; a row that doesn'tcreate_dataset· Create 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 user explicitly askeddelete_dataset· Delete a dataset from a project.get_dataset· Get 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 rows returned againstlist_datasets· List 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 a new tag only when
Show 50 more
update_dataset· Update 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 including every row you wanlist_engines· List 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, WILDCARD is a pattersubmit_feedback· Optional. 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 was missing or confusget_documentation· List 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_monitor· Create 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. Enable it with enable_mdelete_monitor· Delete 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, which needs the "Launcdisable_monitor· Disable 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" access level; belowenable_monitor· Enable 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 enabled, recent Cycles rget_incident· Get 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 happened, read those Cyget_monitor· Get 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 "Launch" access level; belget_monitor_cycle_detail· Get 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_play_status for per-steget_monitoring_summary· Get 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 score 0-100). Drill dlist_incidents· List 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 Incident opens whenlist_monitor_cycles· List 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/until and limit to splist_monitoring_locations· List 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 own Loadster Engines,list_monitors· List 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 and engine ids; readupdate_monitor· Update 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 value, and a list sentget_load_test_report· Get 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 an error naming itsget_load_test_status· Get 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, and each engine's regget_load_test_url_timings· Get 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 name the slow pages belist_load_tests· List 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_load_test launches onestop_load_test· Stop 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 set to true the Loadupdate_load_test_notes· Replace 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 text sent becomes thecreate_scenario· Create 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 the link. The save isdelete_scenario· Delete a scenario from a project. The scripts its populations referenced are left alone.get_scenario· Get 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 estimatedFuelHigh, thlaunch_load_test· Launch 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 and runs the whole tlist_scenarios· List 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. A Scenario is a savupdate_scenario· Update an existing scenario. Each of name, populations, and tags is optional: a field left out keeps its stored value. Populations sent replace the whole list, never merging into it, so to change one, send the others alongside it, each withcreate_project· Create a project for the connected team and return its id, name, and dashboard link. Prefer an existing project: call list_projects first, and create a new one only if the team has none or the user explicitly asked for one. When unsure, askcreate_script· Create a new script in a project. Read the relevant get_documentation topics and use the schema tools first to build valid commands for the bot type. HTTP is a Protocol Bot script, BROWSER is a Browser Bot script, and PLAYWRIGHT is a Playwrdelete_script· Delete a script from a project.delete_script_asset· Delete a file attached to a script.duplicate_script· Duplicate a script, optionally with a new name and into another project the token can access. Returns the copy's summary.get_play_status· Get the current state of a play, with per-step results and log that fill in as it progresses, optionally waiting for it to finish. After play_script, call this with waitSeconds instead of sleeping between polls; the results are complete oncget_script· Get a single script including its full command list and variables, plus a dashboard link. The variables are the script's dataset bindings — the ${...} references in its commands resolve through them.get_script_asset· Read a script asset's content as base64.get_script_revision· Get a specific past revision of a script, including its commands, so you can inspect or diff it.get_step_detail· Read the payloads get_play_status leaves out — response bodies, headers, captured values, console messages, network activity, page HTML, logs — for one or more steps of a play, choosing the parts per call. Ask for several steps at once: a fimport_script· Import an open-source load test (JMeter .jmx, k6 .js, or Locust .py) into an existing script, converting it to Loadster commands. An import may create script assets, datasets, and a scenario; replace=true also replaces the script's existinglist_projects· List the Loadster projects the current token can access, each with its id and name. Every other tool takes one of these ids. When the team has no projects, the result says so and points at create_project. Prefer an existing project: call lilist_script_assets· List the files attached to a script (request bodies, upload files, Playwright support files). Each path is the key a command references.list_script_revisions· List a script's past revisions (newest first) with version, save time, author, and step count.list_scripts· List the scripts in a project with their id, name, bot type, step count, current revision version, and tag names (without the full command list). Tags are shared across the team: to tag an item, reuse a name the list tools already report, aplay_script· Start playing a saved script. Returns immediately with a run id and a queued status, since a play can take anywhere from a few seconds (HTTP) to several minutes (browser or Playwright); read the results with get_play_status.put_script_asset· Upload or replace a script asset from base64 content. Use the path as the key a command references — e.g. set an HTTP command's requestBody to { "key": "<path>" } to give it a request body, or list the path in a browser upload step's files.restore_script_revision· Restore a script to a past revision, saving that revision's commands as a new revision.stop_script· Stop a running play. Errors if the run does not exist; once the stop takes effect, get_play_status reports the run as stopped.update_project· Rename a project and return its id, name, and dashboard link. The project's scripts, scenarios and other contents stay as they are. A name that another project of the team already has is refused. Every write against a user's existing data nupdate_script· Update an existing script. Each of name, type, commands, variables, and tags is optional: a field left out keeps its stored value, an empty list clears that list, and a non-empty list replaces the whole list, never merging into it. A script
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 2.2.1 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://loadster.com/manual/mcp/ | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://api.loadster.com/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/loadster/loadster-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION13 Nov 20262.2.0 → 2.2.1
- VERSION13 Nov 20262.1.0 → 2.2.0
- VERSION12 Nov 20262.0.1 → 2.1.0
- VERSION31 Oct 20261.6.0 → 2.0.1
- VERSION29 Oct 20261.5.0 → 1.6.0
- VERSION28 Oct 20261.4.0 → 1.5.0
- VERSION22 Oct 20261.3.0 → 1.4.0
- VERSION20 Oct 20261.2.0 → 1.3.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Loadster still online?
Free alerts · no account▲ 0Do you run Loadster? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Loadster
How do I connect Loadster?
Use the hosted endpoint https://api.loadster.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Loadster offer?
When Electra Index connected on 15 Nov 2026, it listed 62 tools: get_screenshot, get_command_schema, get_example, get_scripting_api, get_variable_schema, list_command_types, validate_script, append_dataset_rows and more. The full list is in "Live check" above.
Is Loadster online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use Loadster for?
Based on its description, it is most relevant to: test web applications, book appointments online, collect data behind logins, fill web forms automatically.