Everything the Thunders MCP server exposes: 53 tools. If your organization role is Read-only, your assistant sees only the tools marked Read.
Projects and apps
Tool | Access | What it does | Parameters |
| Read | List every project you can access. |
|
| Read | List the apps configured in a project. |
|
Test cases
Tool | Access | What it does | Parameters |
| Read | List test cases with their labels, test sets and steps. The response is large: to find a test case, use |
|
| Read | Find the test cases of a project by text, labels and status. Returns a short summary of each match, the most recently updated first. Use |
|
| Read | Fetch one test case, including its steps. |
|
| Read | List every test case in a project carrying a given label. |
|
| Write | Create an empty test case. |
|
| Write | Duplicate a test case with its steps, settings and test sets. The copy is a Draft named "(Copy)". |
|
| Write | Label a test case. Creates the label if the project does not have it yet. |
|
| Destructive | Delete one or more test cases. A test case reused by another test case is not deleted: it comes back under |
|
| Destructive | Queue test cases for execution. The response gives the |
|
Authoring guide
Tool | Access | What it does | Parameters |
| Read | How to write Thunders test steps: the step types and their JSON, variables, the credit cost of each way to write steps, how a run is judged, and how to fix a failed run. Your assistant reads it once, before it writes or fixes steps. | Optional: |
Test steps
Tool | Access | What it does | Parameters |
| Write | Turn a plain-language scenario into executable steps on a test case. By default it adds steps and changes no existing step. With |
|
| Write | Insert one new step at a given position (0 is first). Thunders assigns the step id. Any step type is supported, including Execute JavaScript: |
|
| Write | Rewrite one existing step. Any step type is supported, including Execute JavaScript. |
|
| Destructive | Delete one step. Every step nested under it is deleted too, and a Conditional step that jumped to a deleted step stops the run instead. |
|
| Destructive | Replace the whole step list of a test case in one write. Keep the |
|
Test sets
Tool | Access | What it does | Parameters |
| Read | List the active test sets in a project (id and name), excluding deleted sets and plans. Use it to resolve a test set name to its id. |
|
| Write | Create a test set, optionally seeded with existing test cases. |
|
| Write | Add a test case to a test set. Does nothing if it is already a member. |
|
| Destructive | Remove a test case from a test set. This changes membership only: it does not delete the test case or the test set. |
|
Schedules
Tool | Access | What it does | Parameters |
| Read | List the schedules of a test set, with their rule, status and next run. |
|
| Write | Run a test set on a recurring rule. Each run uses the test cases that the set holds at run time, so a test case added later is included. |
|
| Write | Change the rule, environment, persona or execution settings of a schedule. Send the whole rule: a field you leave out is not kept. The test set never changes. |
|
| Write | Stop a schedule from running. Past runs stay, and you can resume it later. |
|
| Write | Resume a paused schedule. The next run is computed from now, so missed runs do not run. A schedule that Thunders paused stays paused until you fix the problem. |
|
| Write | Copy a schedule onto the same test set. The copy starts paused, so it cannot run before you check it. |
|
| Destructive | Run the test set of a schedule now, with its saved environment, persona and execution settings. Works on a paused schedule, and does not move the next scheduled run. Refused while a run of the same schedule is in progress, or when your organization has no credits left. |
|
| Destructive | Delete a schedule permanently. Its past runs stay. |
|
Test assets
Tool | Access | What it does | Parameters |
| Read | List the uploaded data files available in a project. |
|
| Write | Upload a data file (CSV, JSON, PDF, image and so on, max 20 MB). Reference it from a test step by its file variable, for example |
|
Step quality suggestions
Thunders reviews authored steps against its authoring best practices before you run them.
Tool | Access | What it does | Parameters |
| Write | List pre-run suggestions for a test case, each with a score, the rule violated, and a rewritten step. It counts as a write because the first call generates and stores the evaluation. |
|
| Destructive | Replace the step's text with the suggested rewrite. |
|
| Write | Hide a suggestion. Leaves the step untouched. |
|
Test runs
Tool | Access | What it does | Parameters |
| Read | List runs for a project, newest first, one page at a time. A test set execution shows as one row. |
|
| Read | List runs across everything you can access, newest first, one page at a time. |
|
| Read | Fetch one run's record, with its status name and, for a failed run, the failed step and the reason. The step recap is left out unless you ask for it. |
|
| Read | The full debugging picture for one run: scenario, authored steps, environment, persona, variables (secrets redacted), per-step recaps with bug reports, and console logs. This is the one to use when investigating a failure. |
|
| Read | Fetch up to 50 runs in one call, with the same fields as |
|
| Read | Check the status of up to 50 runs in one call, without step recaps. |
|
| Read | Wait until every given run finishes, then return their status. It waits 220 seconds at most: when |
|
| Read | A compact view of one run, to judge whether it proves anything: each step with its status, reasoning and bug reports, and the hosts the run reached. It flags an assertion that may prove nothing, so you can check its screenshot. |
|
| Read | The screenshot taken after an action of a step, as an image, to check the screen instead of the reasoning text. By default, the last action of the step that has one. |
|
| Read | The last runs of one test case, newest first, with their status and environment. |
|
Environments
Tool | Access | What it does | Parameters |
| Read | List a project's environments. |
|
| Read | Fetch one environment with its variables and credentials. Secret values are masked. |
|
| Write | Create an environment and point each app at a URL. |
|
| Write | Rename an environment or change its per-app URLs. |
|
| Write | Copy an environment with all its variables and credentials. Defaults to "(Clone)". |
|
Environment variables and credentials
Tool | Access | What it does | Parameters |
| Write | Add one variable or secret credential. |
|
| Write | Add many variables in one call. | A list of the above. |
Authenticated Profiles
Tool | Access | What it does | Parameters |
| Read | List the saved Authenticated Profiles of a project. A test can restore a profile instead of running login steps. A profile whose |
|
Personas
Tool | Access | What it does | Parameters |
| Read | List the personas available for execution. | None |
