octomind-mcp
OfficialThe octomind-mcp server enables developers to integrate Octomind's end-to-end (e2e) testing platform into their local development environment for creating, executing, and managing automated tests.
Key capabilities include:
Search Documentation: Query Octomind's documentation
Test Management: Create, retrieve, and execute test cases
Environment Control: List, create, update, or delete test environments
Test Reporting: Access test execution reports
Test Target Administration: Create, update, or delete test targets (projects/applications)
Private Locations: Configure testing behind firewalls or VPNs
Server Configuration: Get server version, configure session storage (in-memory/Redis), and adjust logging settings
Integration Support: Provides configuration examples for various clients
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@octomind-mcp execute tests for our checkout flow on staging"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
octomind mcp server: let agents create and manage e2e tests
Octomind provides a whole e2e platform for test creation, execution and management including auto-fix. With this MCP server you can use Octomind tools and resources in your local development environment and enable it to create new e2e tests, execute them and more. see https://octomind.dev/ and https://octomind.dev/docs/mcp/install-octomind-mcp for more details.
See it in action together with testrail mcp

Related MCP server: mcp-playwright-test
Configuration
Environment Variables
The server uses the following environment variables:
APIKEY- The API key for Octomind API (required)OCTOMIND_API_URL- Base URL for the API endpoint to use (defaults to https://app.octomind.dev/api)REDIS_URL- Redis connection URL for session storage (optional, format: redis://host:port)SESSION_EXPIRATION_SECONDS- Time in seconds after which sessions expire (optional, Redis only)
Command Line Options
The server supports the following command line options:
-s, --sse- Enable SSE transport mode-t, --stream- Enable Streamable HTTP transport mode-c, --clients- Show client configuration examples-p, --port <port>- Port to listen on (default: 3000)-r, --redis-url <url>- Redis URL for session storage-e, --session-expiration <seconds>- Session expiration time in seconds
Session Storage
The server supports two types of session storage:
In-memory storage (default) - Sessions are stored in memory and will be lost when the server restarts
Redis storage - Sessions are stored in Redis and can persist across server restarts
For production deployments, it's recommended to use Redis storage with an appropriate session expiration time. The Redis storage option also enables horizontal scaling with multiple server instances.
Logging Configuration
LOG_FILENAME- The file to write logs to (only for debugging). If not set, logging is disabledLOG_LEVEL- The log level to use (defaults to info)
Tools
The following tools are implemented in this MCP server:
search- Search the Octomind documentation for a given querygetTestCase- Retrieve a test case for a given test target and test case IDexecuteTests- Trigger test execution for a given test target on a specified URLgetEnvironments- List environments for a test targetcreateEnvironment- Create a new environment for a test targetupdateEnvironment- Update an existing environmentdeleteEnvironment- Delete an environmentgetTestReports- Retrieve test reports for a test targetgetTestReport- Get a specific test report by IDdiscovery- Create a test case with a description or promptgetPrivateLocations- List all private locations configured for the organizationgetVersion- Get the current version of the Octomind MCP server
Installation
You can get configuration snippets for different clients by running:
npx @octomind/octomind-mcp --clientsThis will output configuration examples for Claude Desktop, Cursor, and Windsurf. Here are the configuration files for most clients:
Installing via Smithery
To install octomind-mcp for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claudeClaude Desktop (.claude-config.json)
{
"mcpServers": {
"octomind-mcp": {
"name": "Octomind MCP Server",
"command": "npx",
"args": [
"-y",
"@octomind/octomind-mcp@latest"
],
"env": {
"APIKEY": "your-api-key-here"
}
}
}
}Cursor (cursor.json)
{
"mcpServers": {
"octomind-mcp": {
"name": "Octomind MCP Server",
"command": "npx",
"args": [
"-y",
"@octomind/octomind-mcp@latest"
],
"env": {
"APIKEY": "your-api-key-here"
}
}
}
}Windsurf (mcp_config.json)
{
"mcpServers": {
"octomind-mcp": {
"name": "Octomind MCP Server",
"command": "npx",
"args": [
"-y",
"@octomind/octomind-mcp@latest"
],
"environment": {
"APIKEY": "your-api-key-here"
}
}
}
}Note: Replace your-api-key-here with your actual API key.
To get an APIKEY see here https://octomind.dev/docs/get-started/execution-without-ci#create-an-api-key
Listings / Integrations
Certified by MCPHub
Available Tools
16 toolscreateEnvironmentC
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.
Inputs: name (required), discoveryUrl (required), testTargetId (required), basicAuth, +3 more.
createTestTargetB
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.
Inputs: app (required), discoveryUrl (required), skipAutomaticTestCreation.
deleteEnvironmentB
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.
Inputs: testTargetId (required), environmentId (required).
deleteTestTargetA
the deleteTestTarget tool can delete an existing test target. This operation cannot be undone.
Inputs: testTargetId (required).
discoveryA
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.
Inputs: name (required), prompt (required), testTargetId (required), tagNames, +4 more.
executeTestsC
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.
Inputs: url (required), testTargetId (required), tags, description, +2 more.
getEnvironmentsB
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.
Inputs: testTargetId (required).
getPrivateLocationsA
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.
Inputs: no named parameters.
getTestCaseA
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.
Inputs: testCaseId (required), testTargetId (required).
getTestReportB
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.
Inputs: testReportId (required), testTargetId (required).
getTestReportsC
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.
Inputs: testTargetId (required), key, filter.
getTestTargetsB
the getTestTargets tool can retrieve all test targets or projects. Test targets represent applications or services that can be tested using Octomind.
Inputs: no named parameters.
getVersionA
Returns the current version of the Octomind MCP server
Inputs: no named parameters.
searchA
the search tool can be used to search the octomind documentation for a given query. The search results are returned as a list of links to the documentation.
Inputs: query (required).
updateEnvironmentC
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 include a test account when necsesary to login, a header configuration, a discovery url and a set of variables.
Inputs: testTargetId (required), environmentId (required), name, basicAuth, +4 more.
updateTestTargetC
the updateTestTarget tool can update an existing test target. A test target represents an application or service that can be tested using Octomind.
Inputs: testTargetId (required), app, discoveryUrl, timeoutPerStep, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose: CRUD for environments and test targets, test execution, reporting, search, and version info. No overlap or ambiguity.
All tool names use camelCase consistently, with a verb+noun pattern for most (e.g., createEnvironment, deleteTestTarget). Two single-word names ('discovery', 'search') deviate slightly but remain in the same style.
16 tools cover the domain thoroughly without being excessive. The scope (managing test targets, environments, test cases, reports, execution, and configuration) justifies the count.
Core CRUD operations exist for environments and test targets. Missing operations include updating/deleting test cases and deleting reports, but the main workflows are covered.
Maintenance
Related MCP Connectors
The official MCP Server from Mia-Platform to interact with Mia-Platform Console
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP server for interacting with the Supabase platform
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for autonomous end-to-end testing with Wopee.io. Analyzes web applications, generates and executes Playwright-based functional tests, and validates results — all driven by natural language commands.17881 npm4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that automates Playwright-based UI and API testing, supporting test case generation from requirements or API specs, and execution with detailed reports.12 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes the Pinchtab browser API for token-efficient web scraping, change detection, and automated testing workflows.15MIT
- AlicenseBqualityDmaintenanceA production-ready MCP server that exposes Selenium 4 browser automation as MCP tools.2723 PyPIMIT