Everything the Thunders MCP server exposes: 33 tools.
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 and test sets. |
|
| 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. |
|
Test steps
Tool | Access | What it does | Parameters |
| Write | Turn a plain-language scenario into executable steps on a test case. |
|
| Write | Insert one new step at a given position (0 is first). Any step type is supported, including Execute JavaScript. |
|
| Write | Rewrite one existing step. Any step type is supported, including Execute JavaScript. |
|
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. |
|
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. |
|
| Read | List runs across everything you can access. |
|
| Read | Fetch one run's record. |
|
| 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. |
|
Environments
Tool | Access | What it does | Parameters |
| Read | List a project's environments. |
|
| 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. |
Personas
Tool | Access | What it does | Parameters |
| Read | List the personas available for execution. | None |
