About OctoMind-dev/octomind-mcp
OctoMind-dev/octomind-mcp is an MCP server published by OctoMind-dev in the Data category: an MCP server for octomind tools, resources and prompts.
The repository has 24 stars and 11 forks, with the last commit 3 months ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/OctoMind-dev/octomind-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (12)
createEnvironmentCreate a new environment for a test target
Parameters not published.
deleteEnvironmentDelete an environment
Parameters not published.
discoveryCreate a test case with a description or prompt
Parameters not published.
executeTestsTrigger test execution for a given test target on a specified URL
Parameters not published.
getEnvironmentsList environments for a test target
Parameters not published.
getPrivateLocationsList all private locations configured for the organization
Parameters not published.
getTestCaseRetrieve a test case for a given test target and test case ID
Parameters not published.
getTestReportGet a specific test report by ID
Parameters not published.
getTestReportsRetrieve test reports for a test target
Parameters not published.
getVersionGet the current version of the Octomind MCP server
Parameters not published.
searchSearch the Octomind documentation for a given query
Parameters not published.
updateEnvironmentUpdate an existing environment
Parameters not published.
Ask AI
Ask AI about OctoMind-dev/octomind-mcp
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository yesterday. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
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
README fetched from the repository yesterday. The original is authoritative.

