Skip to main content
Glama
octomind-mcp

octomind-mcp

Official
by OctoMind-dev

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

Video Title

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:

  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

Available Tools

16 tools
createEnvironmentC

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.

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

    A3.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: CRUD for environments and test targets, test execution, reporting, search, and version info. No overlap or ambiguity.

    Naming Consistency4/5

    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.

    Tool Count5/5

    16 tools cover the domain thoroughly without being excessive. The scope (managing test targets, environments, test cases, reports, execution, and configuration) justifies the count.

    Completeness4/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers