Octomind Mcp Server: Let Agents Create And Manage E2e Tests

Overview

What is Octomind MCP?

Octomind MCP is a server specifically designed for Octomind tools, resources, and prompts. It acts as a centralized hub for users to access various functionalities and tools that enhance their productivity and creativity. This platform is especially useful for developers, researchers, and anyone looking to streamline their workflow with effective tools.

Features of Octomind MCP

Centralized Resource Access: Users can easily find a variety of tools and resources in one place, making it convenient to locate what they need.
User-Friendly Interface: The platform is designed with usability in mind, ensuring that users can navigate and use the tools without any difficulty.
Community Support: As a public repository, users can contribute to the project, share their insights, and collaborate with others in the community.
Open Source: Octomind MCP is open-source, allowing developers to modify and enhance the platform according to their needs.
Regular Updates: The repository is actively maintained, with regular updates that introduce new features and improvements.

How to Use Octomind MCP

Access the Repository: Visit the Octomind MCP GitHub page to explore the available resources.
Clone the Repository: Use Git to clone the repository to your local machine for development or personal use.
Explore the Tools: Get familiar with the various tools and resources available within the MCP server.
Contribute: If you have ideas or improvements, consider contributing to the project by submitting pull requests or reporting issues.
Stay Updated: Follow the repository for updates and new releases to ensure you are using the latest version of the tools.

Frequently Asked Questions

What is the purpose of Octomind MCP?

Octomind MCP aims to provide a centralized platform for accessing tools and resources that enhance productivity and creativity for users.

Is Octomind MCP free to use?

Yes, Octomind MCP is an open-source project, making it free for anyone to use, modify, and distribute.

How can I contribute to Octomind MCP?

You can contribute by forking the repository, making changes, and submitting a pull request. Additionally, you can report issues or suggest new features.

Where can I find documentation for Octomind MCP?

Documentation can typically be found within the repository itself, often in a dedicated README.md file or a docs folder.

Can I use Octomind MCP for commercial purposes?

Yes, as an open-source project, you can use Octomind MCP for commercial purposes, but be sure to comply with the licensing terms specified in the repository.

Details

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 disabled
LOG_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 query
getTestCase - Retrieve a test case for a given test target and test case ID
executeTests - Trigger test execution for a given test target on a specified URL
getEnvironments - List environments for a test target
createEnvironment - Create a new environment for a test target
updateEnvironment - Update an existing environment
deleteEnvironment - Delete an environment
getTestReports - Retrieve test reports for a test target
getTestReport - Get a specific test report by ID
discovery - Create a test case with a description or prompt
getPrivateLocations - List all private locations configured for the organization
getVersion - 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

{ "mcpServers": { "octomind-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/metorial/mcp-container--octomind-dev--octomind-mcp--octomind-mcp", "node ./dist/index.js" ], "env": { "APIKEY": "apikey" } } } }