Loading...
Octomind MCP server enables agents to create, execute, and manage end-to-end tests within a local development environment, leveraging Octomind's platform.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Octomind MCP server enables agents to create, execute, and manage end-to-end tests within a local development environment, leveraging Octomind's platform.
The Octomind MCP server offers a mix of read and write operations. It's relatively safe for read-only operations like searching documentation or retrieving test reports. However, creating, updating, or deleting environments and executing tests pose a higher risk and should be carefully monitored.
Performance will depend on the complexity of the tests and the resources available to the server. Consider using Redis for session storage to improve performance and scalability.
Cost considerations include the Octomind API usage, which may have associated costs depending on the usage tier. Redis usage may also incur costs depending on the chosen Redis provider and resources.
npx @octomind/octomind-mcp --clients{
"mcpServers": {
"octomind-mcp": {
"name": "Octomind MCP Server",
"command": "npx",
"args": [
"-y",
"@octomind/octomind-mcp@latest"
],
"env": {
"APIKEY": "your-api-key-here"
}
}
}
}APIKEYREDIS_URLsearchSearches the Octomind documentation for a given query.
Read-only operation with no side effects.
getTestCaseRetrieves a test case for a given test target and test case ID.
Read-only operation; retrieves existing data.
executeTestsTriggers test execution for a given test target on a specified URL.
Executes tests, potentially modifying the state of the target system.
getEnvironmentsLists environments for a test target.
Read-only operation; lists existing environments.
createEnvironmentCreates a new environment for a test target.
Creates a new environment, potentially consuming resources.
updateEnvironmentUpdates an existing environment.
Modifies an existing environment, potentially disrupting tests.
deleteEnvironmentDeletes an environment.
Deletes an environment, potentially disrupting tests and losing configuration.
getTestReportsRetrieves test reports for a test target.
Read-only operation; retrieves existing reports.
getTestReportGets a specific test report by ID.
Read-only operation; retrieves a specific report.
discoveryCreates a test case with a description or prompt.
Creates a new test case, potentially consuming resources.
getPrivateLocationsLists all private locations configured for the organization.
Read-only operation; lists existing locations.
getVersionGets the current version of the Octomind MCP server.
Read-only operation; retrieves server version information.
API Key
cloud
The Octomind MCP server offers a mix of read and write operations. It's relatively safe for read-only operations like searching documentation or retrieving test reports. However, creating, updating, or deleting environments and executing tests pose a higher risk and should be carefully monitored.
The server allows for both read and write operations, including potentially destructive actions like deleting environments. There is no built-in sandboxing or rollback support, so caution is advised when granting autonomy.
Production Tip
Use Redis for session storage in production to ensure session persistence and enable horizontal scaling.
It allows agents to create, execute, and manage end-to-end tests using Octomind's platform within a local development environment.
The APIKEY environment variable is required. Optionally, you can set OCTOMIND_API_URL, REDIS_URL, and SESSION_EXPIRATION_SECONDS.
Use the Smithery CLI: `npx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude` or manually configure .claude-config.json.
The server supports in-memory storage (default) and Redis storage.
Set the REDIS_URL environment variable to the Redis connection URL.
See https://octomind.dev/docs/get-started/execution-without-ci#create-an-api-key.
Compromised API key, improperly configured test environments, and lack of detailed RBAC are potential risks.