createBatchGeneration
create a batch discovery for a given test target. Useful to generate multiple test cases from a prompt and optional images in one go
LABSCO SUMMARY
Writing a test becomes writing a prompt, and the loop from there to a red-or-green report never leaves the conversation.
Three separate generation paths — a single discovery, a batch from one prompt and images, a set built from a written test plan — are the reason to reach for this rather than the dashboard, and executeTests with getTestReport closes the loop in the same session. Repairs are finer-grained than authoring: updateTestCaseElement changes one element's locator line at a time, so a broken selector is quick and a restructured page is not.
What it is
A server over Octomind's end-to-end testing platform, 20 tools spanning test targets, environments, generated test cases, executions and reports.
What you get
- Test targets — the applications under test — created, listed, updated and deleted, with settings such as testIdAttribute and timeoutPerStep
- Environments per target holding a discovery URL, a test account, header configuration, basic auth and variables, created, updated and deleted
- Test cases generated from a prompt by discovery, many at once by createBatchGeneration with optional images, or from freeform plan text by createFromTestPlan
- executeTests triggering a run against a URL for a chosen environment, with tags and per-run variable overrides
- Reports listed and fetched per target, and the individual test case behind a result retrieved with its interactions and assertions
- Existing cases edited after the fact — description, folder, tags, run status — and updateTestCaseElement reaching a single step's locator line
- Private locations listed, which is how a target behind a firewall or VPN gets reached
Requirements
An Octomind account and its key in APIKEY. Tests run against a URL you supply, so the deployment has to be reachable from Octomind — for one that is not, an environment needs a private location configured for your organisation.
Setup effort
One command plus a key — npx @octomind/octomind-mcp --clients, then supply credentials
USE CASES
01
Turning a written test plan into runnable cases
Hand over the plan as freeform text with any screenshots attached, or generate a batch from a single prompt, then list what came back before anything runs.
02
Running the suite against a preview deployment
Pick the environment holding the right test account and headers, trigger the run against the preview URL with any variables overridden for it, then read the report the run produced.
03
Working out why last night's run went red
List the recent reports for the target, open the one that failed, and pull the individual case behind the failure to see the interactions and assertions it was making.
04
Onboarding an application that sits behind a VPN
Register the application as a test target, find which private location can reach it, and create the environment that ties the two together with its login account and headers.
05
Repairing a case after a selector changed
Update the single element whose locator broke rather than regenerating the case, and adjust the case's own status, folder or tags so the suite reflects what is now true.
20 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
createEnvironment
the createEnvironment tool can create an environment for a given test target. an environment represents a specific setup or deployments for a test target. It include a test account when necsesary to login, a header configuration, a discovery url and a set of variables.
createFromTestPlan
create test cases from a test plan for a given test target. Provide freeform text, related images and tag names to assign
createTestTarget
the createTestTarget tool can create a new test target or project. A test target represents an application or service that can be tested using Octomind.
deleteEnvironment
deleteEnvironment tool can delete an environment for a given test target. The environment id is unique to the test target. The call is not reversible. an environment represents a specific setup or deployments for a test target. It include a test account when necsesary to login, a header configuration, a discovery url and a set of variables.
deleteTestTarget
the deleteTestTarget tool can delete an existing test target. This operation cannot be undone.
discovery
the discovery tool can create a test case on a given test target with a test case description or prompt. One can either start from the predefined url for that test case or provide a new entry point url.
executeTests
the executeTests tool can trigger a set of tests for a given test target. The test target id is unique to the test target. The tests are executed on the provided url. The context object is used to provide information about the source of the test execution.
getEnvironments
the getEnvironments tool can retrieve environments for a given test target. an environment represents a specific setup or deployments for a test target. It include a test account when necsesary to login, a header configuration, a discovery url and a set of variables.
getPrivateLocations
the getPrivateLocations tool can retrieve all private locations configured for that org. A private location is a server that can be used to access a test target behind a firewall or VPN.
getTestCase
the getTestCase tool can retrieve a test case for a given test target and test case id. A test case id is unique to the test target. The test case includes a set of interactions and assertions. it is the result of a discovery or a manual creation.
getTestCases
the getTestCases tool can retrieve test cases for a given test target with optional filtering. Test cases can be filtered by various criteria such as status, description, or tags.
getTestReport
the getTestReport tool can retrieve a test report for a given test target and test report id. A test report id is generated when a set of test are executed on a test target. The test report id is unique to the test target.
getTestReports
the getTestReports tool can retrieve test reports for a given test target. Test reports are generated when set of tests are executed. The test report id is unique to the test target.
getTestTargets
the getTestTargets tool can retrieve all test targets or projects. Test targets represent applications or services that can be tested using Octomind.
getVersion
Returns the current version of the Octomind MCP server
updateEnvironment
the updateEnvironment tool can update an environment for a given test target. An environment represents a specific setup or deployments for a test target. It includes a test account when necessary to login, a header configuration or a discovery url.
updateTestCase
the updateTestCase tool can update specific properties of a test case. This allows modifying test case details such as description, status, or folderName.
updateTestCaseElement
the updateTestCaseElement tool can update a specific element within a test case. Test case elements represent individual steps in a test case, such as interactions (clicks, text input) or assertions (checking if elements are visible, have text, etc.). Each element has selectors that identify the target element on the page and an action to perform or assertion to verify. You can only update the locatorLine of the element in question, for everything else the user currently needs to use the octomind ui.
updateTestTarget
the updateTestTarget tool can update an existing test target. A test target represents an application or service that can be tested using Octomind.
BEFORE YOU INSTALL
What to know first
Tools you get
20 tools when we connected. The documentation lists only twelve and omits most writes, such as createTestTarget, deleteTestTarget and updateTestCase. search, documented for searching Octomind documentation, is not currently exposed.
Requires
- npx on PATH
- APIKEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 20 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @octomind/octomind-mcp --clientsMCP Clients
Claude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"octomind-mcp": {
"name": "Octomind MCP Server",
"command": "npx",
"args": [
"-y",
"@octomind/octomind-mcp@latest"
],
"env": {
"APIKEY": "<YOUR_APIKEY>"
}
}
}
}
