
Octomind (E2E Test Automation)
OfficialConnects to the Octomind platform to create, run, and manage end-to-end web tests directly from your development environment using AI.
Enables AI-driven test automation through the Octomind platform for creating, executing, and analyzing end-to-end tests without leaving your development environment.
What it does
- Create new end-to-end tests
- Execute existing test suites
- Analyze test results and failures
- Manage test configurations
- Auto-fix failing tests
- Access Octomind platform resources
Best for
About Octomind (E2E Test Automation)
Octomind (E2E Test Automation) is an official MCP server published by octomind-dev that provides AI assistants with tools and capabilities via the Model Context Protocol. Octomind offers AI-powered software testing and automation, enabling easy end-to-end test creation, execution, and analy It is categorized under developer tools.
How to install
You can install Octomind (E2E Test Automation) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
Octomind (E2E Test Automation) is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
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
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 --clients
This 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 claude
Claude 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
Alternatives
Related Skills
Browse all skillsComprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke for browser automation, E2E tests, Page Object Model, test flakiness, visual testing.
Use when writing new Playwright E2E tests or adding test cases. Provides testing philosophy, patterns, and best practices from the Playwright Developer Handbook.
Use when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables, plugins), (4) Server extensions (API routes, middleware), (5) Releasing/publishing modules to npm, (6) Setting up CI/CD workflows for modules. Provides defineNuxtModule patterns, Kit utilities, hooks, E2E testing, and release automation.
Comprehensive CrewAI framework guide for building collaborative AI agent teams and structured workflows. Use when developing multi-agent systems with CrewAI, creating autonomous AI crews, orchestrating flows, implementing agents with roles and tools, or building production-ready AI automation. Essential for developers building intelligent agent systems, task automation, and complex AI workflows.

