MCP server
by octomind-dev
Octomind offers AI-powered software testing and automation, enabling easy end-to-end test creation, execution, and analy
Connects to the Octomind platform to create, run, and manage end-to-end web tests directly from your development environment using AI.
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.
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.
MIT
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We evaluated Octomind (E2E Test Automation) against two servers with overlapping tools; this profile had the clearer scope statement.
Octomind (E2E Test Automation) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, Octomind (E2E Test Automation) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We evaluated Octomind (E2E Test Automation) against two servers with overlapping tools; this profile had the clearer scope statement.
Octomind (E2E Test Automation) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated Octomind (E2E Test Automation) against two servers with overlapping tools; this profile had the clearer scope statement.
Octomind (E2E Test Automation) is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Octomind (E2E Test Automation) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, Octomind (E2E Test Automation) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
According to our notes, Octomind (E2E Test Automation) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 50
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.
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)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 secondsThe server supports two types of session storage:
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.
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)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 serverYou 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:
To install octomind-mcp for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude
{
"mcpServers": {
"octomind-mcp": {
"name": "Octomind MCP Server",
"command": "npx",
"args": [
"-y",
"@octomind/octomind-mcp@latest"
],
"env": {
"APIKEY": "your-api-key-here"
}
}
}
}
{
"mcpServers": {
"octomind-mcp": {
"name": "Octomind MCP Server",
"command": "npx",
"args": [
"-y",
"@octomind/octomind-mcp@latest"
],
"env": {
"APIKEY": "your-api-key-here"
}
}
}
}
{
"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
Certified by MCPHub
<a href="https://glama.ai/mcp/servers/@OctoMind-dev/octomind-mcp"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@OctoMind-dev/octomind-mcp/badge" alt="octomind-mcp MCP server" /> </a>Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.