Skip to main content

Thunders MCP available tools

Written by Ines

Everything the Thunders MCP server exposes: 33 tools.

Projects and apps

Tool

Access

What it does

Parameters

get_all_projects

Read

List every project you can access.

filter, orderBy, first, all optional. Filter and sort on id, name, url.

get_apps_by_project_id

Read

List the apps configured in a project.

projectId

Test cases

Tool

Access

What it does

Parameters

get_all_test_cases

Read

List test cases with their labels and test sets.

projectId (strongly recommended), first, orderBy, all optional.

get_test_case_by_id

Read

Fetch one test case, including its steps.

id

get_test_cases_by_label

Read

List every test case in a project carrying a given label.

projectId, labelName

create_test_case

Write

Create an empty test case.

projectId. Optional: name, description, executionPlatform (Web or Mobile), reusedTests.

clone_test_case

Write

Duplicate a test case with its steps, settings and test sets. The copy is a Draft named "(Copy)".

id

add_label_to_test_case

Write

Label a test case. Creates the label if the project does not have it yet.

testCaseId, projectId, labelName

delete_test_case

Destructive

Delete one or more test cases. A test case reused by another test case is not deleted: it comes back under reusedIds and stays in place, so check deletedIds to confirm what actually went. If any id belongs to another organization the whole call is rejected.

testCaseIds (a list, so one call can remove several)

queue_test_cases

Destructive

Queue test cases for execution.

testCaseIds, projectId, environmentId, personaId. Optional: browserSettings, maxParallelism, maxRetries, alwaysRerun, executionMode (parallel or sequential), failureBehavior (continue or stop), variables, testAssetReferences.

Test steps

Tool

Access

What it does

Parameters

generate_test_steps

Write

Turn a plain-language scenario into executable steps on a test case.

testCaseId. Optional: scenario, personaId, projectId, language (for example en, fr), stage (Main or Teardown), attachmentIds.

insert_step

Write

Insert one new step at a given position (0 is first). Any step type is supported, including Execute JavaScript.

testCaseId, step, position. Optional: knownUpdatedAt for conflict detection.

update_test_step

Write

Rewrite one existing step. Any step type is supported, including Execute JavaScript.

testCaseId, step. Optional: knownUpdatedAt for conflict detection.

Test sets

Tool

Access

What it does

Parameters

get_test_sets

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.

projectId

create_test_set

Write

Create a test set, optionally seeded with existing test cases.

projectId. Optional: name, testCases.

add_test_case_to_test_set

Write

Add a test case to a test set. Does nothing if it is already a member.

testCaseId, plus exactly one of testSetId or testSetName. A name must match exactly one test set in the test case's own project.

remove_test_case_from_test_set

Destructive

Remove a test case from a test set. This changes membership only: it does not delete the test case or the test set.

testCaseId, plus exactly one of testSetId or testSetName.

Test assets

Tool

Access

What it does

Parameters

list_test_assets

Read

List the uploaded data files available in a project.

projectId

upload_test_asset

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 [FILE_CUSTOMERS_CSV].

projectId, fileName (with extension), contentBase64. Optional: testId to associate it with a test case.

Step quality suggestions

Thunders reviews authored steps against its authoring best practices before you run them.

Tool

Access

What it does

Parameters

get_test_case_suggestions

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.

testCaseId

apply_test_case_suggestion

Destructive

Replace the step's text with the suggested rewrite.

testCaseId, suggestionId

dismiss_test_case_suggestion

Write

Hide a suggestion. Leaves the step untouched.

testCaseId, suggestionId

Test runs

Tool

Access

What it does

Parameters

get_test_runs_by_project_id

Read

List runs for a project.

projectId. Optional: filter, orderBy, first, label.

get_all_test_runs

Read

List runs across everything you can access.

filter, orderBy, first, all optional. Filter on id, test_case_id, test_set_id, status, run_at.

get_test_run_by_id

Read

Fetch one run's record.

id

get_test_run_context

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.

id

Environments

Tool

Access

What it does

Parameters

get_environments_by_project_id

Read

List a project's environments.

projectId

create_environment

Write

Create an environment and point each app at a URL.

projectId, name. Optional: description, apps (an appId plus url per app).

update_environment

Write

Rename an environment or change its per-app URLs.

environmentId, name. Optional: description, apps.

clone_environment

Write

Copy an environment with all its variables and credentials. Defaults to "(Clone)".

environmentId. Optional: name.

Environment variables and credentials

Tool

Access

What it does

Parameters

create_environment_variable

Write

Add one variable or secret credential.

environmentId, projectId, name, value, isSecret. Optional: description. Names are uppercase A to Z, 0 to 9 and underscores, max 30 characters.

create_environment_variables

Write

Add many variables in one call.

A list of the above.

Personas

Tool

Access

What it does

Parameters

get_all_personas

Read

List the personas available for execution.

None

Did this answer your question?