Octomind MCP Server

What is Octomind MCP Server about?

Enables local development environments to interact with Octomind’s e2e testing platform. Agents can create new tests, retrieve existing ones, execute them, and manage test environments and reports via a configurable MCP server.

How to use Octomind MCP Server?

1. Install the server with npx:

   npx -y @octomind/octomind-mcp
   

2. Provide the required APIKEY environment variable (obtainable from the Octomind dashboard).
3. Optionally configure Redis for persistent session storage using REDIS_URL and SESSION_EXPIRATION_SECONDS.
4. Run the server (default port 3000) and connect your client (Claude Desktop, Cursor, Windsurf, etc.) using the generated configuration snippets.

Key Features

• Test lifecycle management: search, getTestCase, executeTests, discovery and report retrieval.
• Environment handling: list, create, update, and delete test environments.
• Session storage options: in‑memory (default) or Redis for horizontal scaling.
• Transport modes: Server‑Sent Events (SSE) and streamable HTTP.
• Extensible logging via LOG_FILENAME and LOG_LEVEL.
• Ready‑made client configurations for Claude Desktop, Cursor, and Windsurf.

Use Cases

• Integrate automated end‑to‑end testing into CI/CD pipelines without requiring a full Octomind cloud deployment.
• Provide AI agents (e.g., Claude) the ability to generate and run tests on‑the‑fly during a development session.
• Centralize test execution reports and environment data across multiple developer machines using Redis.
• Enable rapid prototyping of test scenarios via the discovery tool that accepts natural‑language prompts.

FAQ

Q: What is the minimum required configuration? A: Set the APIKEY environment variable; the server will run with in‑memory session storage on port 3000.

Q: How do I enable persistent sessions? A: Provide a REDIS_URL (e.g., redis://localhost:6379) and optionally SESSION_EXPIRATION_SECONDS.

Q: Can I change the listening port? A: Yes, use the -p or --port CLI option, e.g., npx -y @octomind/octomind-mcp -p 4000.

Q: Which transport mode should I choose? A: SSE (-s/--sse) for push‑based updates, or streamable HTTP (-t/--stream) for traditional request/response.

Q: Where can I find API documentation? A: Visit https://octomind.dev/ and https://octomind.dev/docs/mcp/install-octomind-mcp.

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:

1. In-memory storage (default) - Sessions are stored in memory and will be lost when the server restarts
2. 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