[{"_1":2,"_348":-5,"_349":-5},"loaderData",{"_3":4,"_29":30,"_272":273},"root",{"_5":6,"_14":15},"toasts",[7],{"_8":9,"_10":11,"_12":13},"uid","0199fa89-d09e-70a1-8992-d79408dfc9cf","title","You need to sign in to access this page","type","error","visitor",{"_16":17,"_18":19},"viewportWidth",1280,"visitorSession",{"_20":21,"_23":24,"_25":-5,"_26":27,"_28":-5},"attributes",[22],"bot","id",19346472,"membership","referenceId","0199f420-7955-7299-8090-ea86aef37824","userAccount","routes/_public/mcp/servers/~namespace/~slug/_pages/_layout",{"_31":32,"_86":-5,"_87":45,"_34":88,"_188":189,"_270":271},"availableLocales",[33,45,52,58,65,72,79],{"_34":35,"_38":42,"_43":44},"mcpServer",{"_36":37,"_38":39,"_40":41},"description","MCP-Server zur Interaktion mit der Octomind-Plattform. Octomind bietet Lösungen zum Erstellen, Ausführen und Reparieren von E2E-Webtests, siehe [https://octomind.dev](https://octomind.dev)","name","Octomind-MCP","readme","# Octomind MCP-Server: Lassen Sie Agenten E2E-Tests erstellen und verwalten\n\n[![Schmiedeabzeichen](https://smithery.ai/badge/@OctoMind-dev/octomind-mcp)](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)\n\nOctomind bietet eine umfassende E2E-Plattform für die Erstellung, Ausführung und Verwaltung von Tests inklusive Auto-Fix. Mit diesem MCP-Server können Sie Octomind-Tools und -Ressourcen in Ihrer lokalen Entwicklungsumgebung nutzen und neue E2E-Tests erstellen, ausführen und vieles mehr. Weitere Informationen finden Sie [unter https://octomind.dev/](https://octomind.dev/) und .\n\n## Sehen Sie es zusammen mit Testrail MCP in Aktion\n\n[![Videotitel](https://img.youtube.com/vi/I7lc9I0S62Y/0.jpg)](https://www.youtube.com/watch?v=I7lc9I0S62Y)\n\n## Konfiguration\n\n### Umgebungsvariablen\n\nDer Server verwendet die folgenden Umgebungsvariablen:\n\n* `APIKEY` – Der API-Schlüssel für die Octomind-API (erforderlich)\n* `OCTOMIND_API_URL` – Basis-URL für den zu verwendenden API-Endpunkt (standardmäßig )\n* `REDIS_URL` – Redis-Verbindungs-URL für Sitzungsspeicher (optional, Format: redis://host:port)\n* `SESSION_EXPIRATION_SECONDS` – Zeit in Sekunden, nach der Sitzungen ablaufen (optional, nur Redis)\n\n### Befehlszeilenoptionen\n\nDer Server unterstützt die folgenden Befehlszeilenoptionen:\n\n* `-s, --sse` – SSE-Transportmodus aktivieren\n* `-t, --stream` – Streambaren HTTP-Transportmodus aktivieren\n* `-c, --clients` – Client-Konfigurationsbeispiele anzeigen\n* `-p, --port ` – Port, auf dem gelauscht wird (Standard: 3000)\n* `-r, --redis-url ` – Redis-URL für Sitzungsspeicher\n* `-e, --session-expiration ` – Ablaufzeit der Sitzung in Sekunden\n\n### Sitzungsspeicher\n\nDer Server unterstützt zwei Arten der Sitzungsspeicherung:\n\n1. **In-Memory-Speicherung** (Standard) – Sitzungen werden im Speicher gespeichert und gehen beim Neustart des Servers verloren\n2. **Redis-Speicher** – Sitzungen werden in Redis gespeichert und können über Serverneustarts hinaus bestehen bleiben\n\nFür Produktionsbereitstellungen wird die Verwendung von Redis-Speicher mit einer entsprechenden Sitzungsablaufzeit empfohlen. Die Redis-Speicheroption ermöglicht außerdem die horizontale Skalierung mit mehreren Serverinstanzen.\n\n### Protokollierungskonfiguration\n\n* `LOG_FILENAME` - Die Datei, in die Protokolle geschrieben werden (nur zum Debuggen). Wenn nicht festgelegt, ist die Protokollierung deaktiviert.\n* `LOG_LEVEL` – Die zu verwendende Protokollebene (standardmäßig „Info“)\n\n## Werkzeuge\n\nDie folgenden Tools sind in diesem MCP-Server implementiert:\n\n* `search` - Durchsuchen Sie die Octomind-Dokumentation nach einer bestimmten Abfrage\n* `getTestCase` - Ruft einen Testfall für ein bestimmtes Testziel und eine bestimmte Testfall-ID ab\n* `executeTests` - Testausführung für ein bestimmtes Testziel unter einer angegebenen URL auslösen\n* `getEnvironments` - Umgebungen für ein Testziel auflisten\n* `createEnvironment` - Erstellen Sie eine neue Umgebung für ein Testziel\n* `updateEnvironment` - Eine vorhandene Umgebung aktualisieren\n* `deleteEnvironment` - Eine Umgebung löschen\n* `getTestReports` - Testberichte für ein Testziel abrufen\n* `getTestReport` - Holen Sie sich einen bestimmten Testbericht nach ID\n* `discovery` - Erstellen Sie einen Testfall mit einer Beschreibung oder Eingabeaufforderung\n* `getPrivateLocations` – Listet alle für die Organisation konfigurierten privaten Standorte auf\n* `getVersion` - Aktuelle Version des Octomind MCP-Servers abrufen\n\n## Installation\n\nSie können Konfigurationsausschnitte für verschiedene Clients erhalten, indem Sie Folgendes ausführen:\n\n```bash\nnpx @octomind/octomind-mcp --clients\n```\n\nEs werden Konfigurationsbeispiele für Claude Desktop, Cursor und Windsurf ausgegeben. Hier sind die Konfigurationsdateien für die meisten Clients:\n\n### Installation über Smithery\n\nSo installieren Sie octomind-mcp für Claude Desktop automatisch über [Smithery](https://smithery.ai/server/@OctoMind-dev/octomind-mcp) :\n\n```bash\nnpx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude\n```\n\n### Claude Desktop (.claude-config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Cursor (cursor.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Windsurfen (mcp\\_config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"environment\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\nHinweis: Ersetzen Sie `your-api-key-here` durch Ihren tatsächlichen API-Schlüssel.\n\nUm einen APIKEY zu erhalten, siehe hier [https://octomind.dev/docs/get-started/executed-without-ci#create-an-api-key](https://octomind.dev/docs/get-started/execution-without-ci#create-an-api-key)\n\n# Listings / Integrationen\n\n[![MseeP.ai-Sicherheitsbewertungsabzeichen](https://mseep.net/pr/octomind-dev-octomind-mcp-badge.png)](https://mseep.ai/app/octomind-dev-octomind-mcp)","German","tag","de-DE",{"_34":46,"_38":50,"_43":51},{"_36":47,"_38":48,"_40":49},"mcp server to interact with the octomind plattform. octomind provides a create, run & fix solutions for e2e web testing, see https://octomind.dev","octomind-mcp","# octomind mcp server: let agents create and manage e2e tests\n\n $\"Octomind$ \n\n[![smithery badge](https://smithery.ai/badge/@OctoMind-dev/octomind-mcp)](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)\n\nOctomind provides a whole e2e platform for test creation, execution and management including auto-fix.\nWith this MCP server you can use Octomind tools and resources in your local development environment and \nenable it to create new e2e tests, execute them and more. see https://octomind.dev/ and \nhttps://octomind.dev/docs/mcp/install-octomind-mcp for more details.\n\n## See it in action together with testrail mcp\n\n[![Video Title](https://img.youtube.com/vi/I7lc9I0S62Y/0.jpg)](https://www.youtube.com/watch?v=I7lc9I0S62Y)\n\n## Configuration\n\n### Environment Variables\n\nThe server uses the following environment variables:\n\n- `APIKEY` - The API key for Octomind API (required)\n- `OCTOMIND_API_URL` - Base URL for the API endpoint to use (defaults to https://app.octomind.dev/api)\n- `REDIS_URL` - Redis connection URL for session storage (optional, format: redis://host:port)\n- `SESSION_EXPIRATION_SECONDS` - Time in seconds after which sessions expire (optional, Redis only)\n\n### Command Line Options\n\nThe server supports the following command line options:\n\n- `-s, --sse` - Enable SSE transport mode\n- `-t, --stream` - Enable Streamable HTTP transport mode\n- `-c, --clients` - Show client configuration examples\n- `-p, --port ` - Port to listen on (default: 3000)\n- `-r, --redis-url ` - Redis URL for session storage\n- `-e, --session-expiration ` - Session expiration time in seconds\n\n### Session Storage\n\nThe server supports two types of session storage:\n\n1. **In-memory storage** (default) - Sessions are stored in memory and will be lost when the server restarts\n2. **Redis storage** - Sessions are stored in Redis and can persist across server restarts\n\nFor 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.\n\n### Logging Configuration\n\n- `LOG_FILENAME` - The file to write logs to (only for debugging). If not set, logging is disabled\n- `LOG_LEVEL` - The log level to use (defaults to info)\n\n## Tools\n\nThe following tools are implemented in this MCP server:\n\n- `search` - Search the Octomind documentation for a given query\n- `getTestCase` - Retrieve a test case for a given test target and test case ID\n- `executeTests` - Trigger test execution for a given test target on a specified URL\n- `getEnvironments` - List environments for a test target\n- `createEnvironment` - Create a new environment for a test target\n- `updateEnvironment` - Update an existing environment\n- `deleteEnvironment` - Delete an environment\n- `getTestReports` - Retrieve test reports for a test target\n- `getTestReport` - Get a specific test report by ID\n- `discovery` - Create a test case with a description or prompt\n- `getPrivateLocations` - List all private locations configured for the organization\n- `getVersion` - Get the current version of the Octomind MCP server\n\n## Installation\n\nYou can get configuration snippets for different clients by running:\n\n```bash\nnpx @octomind/octomind-mcp --clients\n```\n\nThis will output configuration examples for Claude Desktop, Cursor, and Windsurf. Here are the configuration files for most clients:\n\n### Installing via Smithery\n\nTo install octomind-mcp for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@OctoMind-dev/octomind-mcp):\n\n```bash\nnpx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude\n```\n\n### Claude Desktop (.claude-config.json)\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Cursor (cursor.json)\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Windsurf (mcp_config.json)\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"environment\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\nNote: Replace `your-api-key-here` with your actual API key.\n\nTo get an APIKEY see here https://octomind.dev/docs/get-started/execution-without-ci#create-an-api-key\n\n# Listings / Integrations\n\n\n $\"octomind-mcp$ \n\n\n[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/octomind-dev-octomind-mcp-badge.png)](https://mseep.ai/app/octomind-dev-octomind-mcp)\n\n","English","en-US",{"_34":53,"_38":56,"_43":57},{"_36":54,"_38":48,"_40":55},"Servidor mcp para interactuar con la plataforma octomind. octomind ofrece soluciones de creación, ejecución y reparación para pruebas web de extremo a extremo. Consulte [https://octomind.dev](https://octomind.dev)","# Servidor Octomind MCP: permite a los agentes crear y gestionar pruebas de extremo a extremo\n\n[![insignia de herrería](https://smithery.ai/badge/@OctoMind-dev/octomind-mcp)](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)\n\nOctomind ofrece una plataforma completa de extremo a extremo para la creación, ejecución y gestión de pruebas, incluyendo corrección automática. Con este servidor MCP, puede usar las herramientas y recursos de Octomind en su entorno de desarrollo local y habilitarlo para crear nuevas pruebas de extremo a extremo, ejecutarlas y mucho más. Consulte y para obtener más información.\n\n## Véalo en acción junto con testrail mcp\n\n[![Título del vídeo](https://img.youtube.com/vi/I7lc9I0S62Y/0.jpg)](https://www.youtube.com/watch?v=I7lc9I0S62Y)\n\n## Configuración\n\n### Variables de entorno\n\nEl servidor utiliza las siguientes variables de entorno:\n\n* `APIKEY` : la clave API para la API de Octomind (obligatoria)\n* `OCTOMIND_API_URL` : URL base que utilizará el punto final de la API (el valor predeterminado es )\n* `REDIS_URL` : URL de conexión de Redis para el almacenamiento de la sesión (opcional, formato: redis://host:puerto)\n* `SESSION_EXPIRATION_SECONDS` - Tiempo en segundos después del cual las sesiones expiran (opcional, solo Redis)\n\n### Opciones de línea de comandos\n\nEl servidor admite las siguientes opciones de línea de comandos:\n\n* `-s, --sse` - Habilitar el modo de transporte SSE\n* `-t, --stream` - Habilitar el modo de transporte HTTP Streamable\n* `-c, --clients` - Mostrar ejemplos de configuración del cliente\n* `-p, --port ` - Puerto para escuchar (predeterminado: 3000)\n* `-r, --redis-url ` - URL de Redis para el almacenamiento de sesiones\n* `-e, --session-expiration ` - Tiempo de expiración de la sesión en segundos\n\n### Almacenamiento de sesiones\n\nEl servidor admite dos tipos de almacenamiento de sesiones:\n\n1. **Almacenamiento en memoria** (predeterminado): las sesiones se almacenan en la memoria y se perderán cuando se reinicie el servidor.\n2. **Almacenamiento de Redis** : las sesiones se almacenan en Redis y pueden persistir tras reinicios del servidor.\n\nPara implementaciones de producción, se recomienda usar almacenamiento Redis con un tiempo de expiración de sesión adecuado. Esta opción también permite el escalado horizontal con múltiples instancias de servidor.\n\n### Configuración de registro\n\n* `LOG_FILENAME` : El archivo donde se escriben los registros (solo para depuración). Si no se configura, el registro se desactiva.\n* `LOG_LEVEL` : el nivel de registro a utilizar (el valor predeterminado es información)\n\n## Herramientas\n\nLas siguientes herramientas están implementadas en este servidor MCP:\n\n* `search` : busca en la documentación de Octomind una consulta determinada\n* `getTestCase` : recupera un caso de prueba para un objetivo de prueba y un ID de caso de prueba determinados\n* `executeTests` : activa la ejecución de una prueba para un objetivo de prueba determinado en una URL específica\n* `getEnvironments` : enumera los entornos para un objetivo de prueba\n* `createEnvironment` : crea un nuevo entorno para un objetivo de prueba\n* `updateEnvironment` - Actualizar un entorno existente\n* `deleteEnvironment` - Eliminar un entorno\n* `getTestReports` : recupera informes de pruebas para un objetivo de prueba\n* `getTestReport` - Obtenga un informe de prueba específico por ID\n* `discovery` - Crear un caso de prueba con una descripción o mensaje\n* `getPrivateLocations` : enumera todas las ubicaciones privadas configuradas para la organización\n* `getVersion` : obtiene la versión actual del servidor Octomind MCP\n\n## Instalación\n\nPuede obtener fragmentos de configuración para diferentes clientes ejecutando:\n\n```bash\nnpx @octomind/octomind-mcp --clients\n```\n\nEsto generará ejemplos de configuración para Claude Desktop, Cursor y Windsurf. Estos son los archivos de configuración para la mayoría de los clientes:\n\n### Instalación mediante herrería\n\nPara instalar octomind-mcp para Claude Desktop automáticamente a través de [Smithery](https://smithery.ai/server/@OctoMind-dev/octomind-mcp) :\n\n```bash\nnpx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude\n```\n\n### Escritorio de Claude (.claude-config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Cursor (cursor.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Tabla de windsurf (mcp\\_config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"environment\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\nNota: reemplace `your-api-key-here` con su clave API real.\n\nPara obtener una APIKEY, consulte aquí \n\n# Listados / Integraciones\n\n[![Insignia de evaluación de seguridad de MseeP.ai](https://mseep.net/pr/octomind-dev-octomind-mcp-badge.png)](https://mseep.ai/app/octomind-dev-octomind-mcp)","Spanish","es-ES",{"_34":59,"_38":63,"_43":64},{"_36":60,"_38":61,"_40":62},"octomind プラットフォームと対話するための mcp サーバー。octomind は、e2e Web テストの作成、実行、修正ソリューションを提供します。https [://octomind.dev を](https://octomind.dev)参照してください。","オクトマインド-MCP","# octomind mcp サーバー: エージェントが E2E テストを作成および管理できるようにする\n\n[![鍛冶屋のバッジ](https://smithery.ai/badge/@OctoMind-dev/octomind-mcp)](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)\n\nOctomindは、テストの作成、実行、管理、そして自動修正機能を含む包括的なE2Eプラットフォームを提供します。このMCPサーバーを使用すると、ローカル開発環境でOctomindのツールとリソースを使用し、新しいE2Eテストの作成や実行などが可能になります。詳細については、およびをご覧ください。\n\n## testrail mcp と一緒に動作を確認してください\n\n[![ビデオタイトル](https://img.youtube.com/vi/I7lc9I0S62Y/0.jpg)](https://www.youtube.com/watch?v=I7lc9I0S62Y)\n\n## 構成\n\n### 環境変数\n\nサーバーは次の環境変数を使用します。\n\n* `APIKEY` - Octomind API の API キー (必須)\n* `OCTOMIND_API_URL` - 使用する API エンドポイントのベース URL (デフォルトは )\n* `REDIS_URL` - セッション保存用のRedis接続URL（オプション、形式：redis://host:port）\n* `SESSION_EXPIRATION_SECONDS` - セッションの有効期限が切れるまでの時間（秒）（オプション、Redis のみ）\n\n### コマンドラインオプション\n\nサーバーは次のコマンドラインオプションをサポートしています。\n\n* `-s, --sse` - SSEトランスポートモードを有効にする\n* `-t, --stream` - ストリーミング可能なHTTPトランスポートモードを有効にする\n* `-c, --clients` - クライアント設定例を表示\n* `-p, --port ` - リッスンするポート（デフォルト: 3000）\n* `-r, --redis-url ` - セッション保存用のRedis URL\n* `-e, --session-expiration ` - セッションの有効期限（秒）\n\n### セッションストレージ\n\nサーバーは、次の 2 種類のセッションストレージをサポートしています。\n\n1. **メモリ内ストレージ**（デフォルト） - セッションはメモリ内に保存され、サーバーを再起動すると失われます。\n2. **Redis ストレージ**- セッションは Redis に保存され、サーバーの再起動後も保持されます。\n\n本番環境では、適切なセッション有効期限を設定したRedisストレージの使用をお勧めします。Redisストレージオプションは、複数のサーバーインスタンスによる水平スケーリングも可能にします。\n\n### ログ構成\n\n* `LOG_FILENAME` - ログを書き込むファイル（デバッグ専用）。設定されていない場合はログは無効になります。\n* `LOG_LEVEL` - 使用するログレベル（デフォルトはinfo）\n\n## ツール\n\nこの MCP サーバーには次のツールが実装されています。\n\n* `search` - 指定されたクエリでOctomindドキュメントを検索します\n* `getTestCase` - 指定されたテストターゲットとテストケースIDのテストケースを取得します\n* `executeTests` - 指定された URL 上の特定のテストターゲットのテスト実行をトリガーします\n* `getEnvironments` - テストターゲットの環境を一覧表示する\n* `createEnvironment` - テストターゲット用の新しい環境を作成する\n* `updateEnvironment` - 既存の環境を更新する\n* `deleteEnvironment` - 環境を削除する\n* `getTestReports` - テストターゲットのテストレポートを取得する\n* `getTestReport` - IDで特定のテストレポートを取得する\n* `discovery` - 説明またはプロンプトを使用してテストケースを作成する\n* `getPrivateLocations` - 組織に設定されているすべてのプライベートロケーションを一覧表示します\n* `getVersion` - Octomind MCP サーバーの現在のバージョンを取得します\n\n## インストール\n\n次のコマンドを実行すると、さまざまなクライアントの構成スニペットを取得できます。\n\n```bash\nnpx @octomind/octomind-mcp --clients\n```\n\nClaude Desktop、Cursor、Windsurfの設定例が出力されます。ほとんどのクライアントの設定ファイルは次のとおりです。\n\n### Smithery経由でインストール\n\n[Smithery](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)経由で Claude Desktop 用の octomind-mcp を自動的にインストールするには:\n\n```bash\nnpx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude\n```\n\n### クロードデスクトップ (.claude-config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### カーソル (cursor.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### ウィンドサーフィン (mcp\\_config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"environment\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n注: `your-api-key-here`実際の API キーに置き換えてください。\n\nAPIKEY を取得するには、こちらを参照してください。\n\n# リスト/統合\n\n[![MseeP.ai セキュリティ評価バッジ](https://mseep.net/pr/octomind-dev-octomind-mcp-badge.png)](https://mseep.ai/app/octomind-dev-octomind-mcp)","Japanese","ja-JP",{"_34":66,"_38":70,"_43":71},{"_36":67,"_38":68,"_40":69},"Octomind 플랫폼과 상호 작용하는 mcp 서버입니다. Octomind는 e2e 웹 테스트를 위한 생성, 실행 및 수정 솔루션을 제공합니다. 자세한 내용은 [https://octomind.dev를](https://octomind.dev) 참조하세요.","옥토마인드-MCP","# octomind mcp 서버: 에이전트가 e2e 테스트를 생성하고 관리하도록 허용\n\n[![대장간 배지](https://smithery.ai/badge/@OctoMind-dev/octomind-mcp)](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)\n\nOctomind는 테스트 생성, 실행 및 관리를 위한 완전한 e2e 플랫폼을 제공하며, 자동 수정 기능도 포함되어 있습니다. 이 MCP 서버를 사용하면 로컬 개발 환경에서 Octomind 도구와 리소스를 활용하여 새로운 e2e 테스트를 생성하고 실행하는 등의 작업을 수행할 수 있습니다. 자세한 내용은 및 [https://octomind.dev/docs/mcp/install-octomind-mcp를](https://octomind.dev/docs/mcp/install-octomind-mcp) 참조하세요.\n\n## Testrail MCP와 함께 실제 모습을 확인해 보세요.\n\n[![비디오 제목](https://img.youtube.com/vi/I7lc9I0S62Y/0.jpg)](https://www.youtube.com/watch?v=I7lc9I0S62Y)\n\n## 구성\n\n### 환경 변수\n\n서버는 다음과 같은 환경 변수를 사용합니다.\n\n* `APIKEY` - Octomind API용 API 키(필수)\n* `OCTOMIND_API_URL` - 사용할 API 엔드포인트의 기본 URL(기본값은 )\n* `REDIS_URL` - 세션 저장을 위한 Redis 연결 URL(선택 사항, 형식: redis://host:port)\n* `SESSION_EXPIRATION_SECONDS` - 세션이 만료되기까지의 시간(초)(선택 사항, Redis에만 해당)\n\n### 명령줄 옵션\n\n서버는 다음 명령줄 옵션을 지원합니다.\n\n* `-s, --sse` - SSE 전송 모드 활성화\n* `-t, --stream` - 스트리밍 가능한 HTTP 전송 모드 활성화\n* `-c, --clients` - 클라이언트 구성 예시 표시\n* `-p, --port ` - 수신할 포트(기본값: 3000)\n* `-r, --redis-url ` - 세션 저장을 위한 Redis URL\n* `-e, --session-expiration ` - 세션 만료 시간(초)\n\n### 세션 저장소\n\n서버는 두 가지 유형의 세션 저장소를 지원합니다.\n\n1. **메모리 내 저장소** (기본값) - 세션은 메모리에 저장되며 서버가 다시 시작되면 손실됩니다.\n2. **Redis 저장소** - 세션은 Redis에 저장되며 서버를 다시 시작해도 유지됩니다.\n\n프로덕션 배포의 경우, 적절한 세션 만료 시간을 설정한 Redis 스토리지를 사용하는 것이 좋습니다. Redis 스토리지 옵션은 여러 서버 인스턴스를 수평적으로 확장할 수 있도록 지원합니다.\n\n### 로깅 구성\n\n* `LOG_FILENAME` - 로그를 기록할 파일(디버깅 전용). 설정하지 않으면 로깅이 비활성화됩니다.\n* `LOG_LEVEL` - 사용할 로그 수준(기본값은 info)\n\n## 도구\n\n이 MCP 서버에는 다음 도구가 구현되어 있습니다.\n\n* `search` - 주어진 쿼리에 대해 Octomid 문서를 검색합니다.\n* `getTestCase` - 주어진 테스트 대상 및 테스트 케이스 ID에 대한 테스트 케이스를 검색합니다.\n* `executeTests` - 지정된 URL에서 주어진 테스트 대상에 대한 테스트 실행을 트리거합니다.\n* `getEnvironments` - 테스트 대상의 환경 나열\n* `createEnvironment` - 테스트 대상에 대한 새 환경을 만듭니다.\n* `updateEnvironment` - 기존 환경 업데이트\n* `deleteEnvironment` - 환경 삭제\n* `getTestReports` - 테스트 대상에 대한 테스트 보고서 검색\n* `getTestReport` - ID로 특정 테스트 보고서 가져오기\n* `discovery` - 설명이나 프롬프트를 사용하여 테스트 케이스를 만듭니다.\n* `getPrivateLocations` - 조직에 대해 구성된 모든 개인 위치 나열\n* `getVersion` - Octomind MCP 서버의 현재 버전을 가져옵니다.\n\n## 설치\n\n다음을 실행하면 다양한 클라이언트에 대한 구성 스니펫을 얻을 수 있습니다.\n\n지엑스피1\n\nClaude Desktop, Cursor, Windsurf에 대한 구성 예가 출력됩니다. 대부분의 클라이언트에 대한 구성 파일은 다음과 같습니다.\n\n### Smithery를 통해 설치\n\n[Smithery를](https://smithery.ai/server/@OctoMind-dev/octomind-mcp) 통해 Claude Desktop용 octomind-mcp를 자동으로 설치하려면:\n\n```bash\nnpx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude\n```\n\n### 클로드 데스크톱(.claude-config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### 커서(cursor.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### 윈드서핑(mcp\\_config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"environment\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n참고: `your-api-key-here` 실제 API 키로 바꾸세요.\n\nAPIKEY를 얻으려면 여기를 참조하세요 \n\n# 목록/통합\n\n[![MseeP.ai 보안 평가 배지](https://mseep.net/pr/octomind-dev-octomind-mcp-badge.png)](https://mseep.ai/app/octomind-dev-octomind-mcp)","Korean","ko-KR",{"_34":73,"_38":77,"_43":78},{"_36":74,"_38":75,"_40":76},"mcp-сервер для взаимодействия с платформой octomind. octomind предоставляет решения для создания, запуска и исправления ошибок для e2e веб-тестирования, см. [https://octomind.dev](https://octomind.dev)","октоминд-mcp","# сервер octomind mcp: позволяет агентам создавать и управлять тестами e2e\n\n[![значок кузнеца](https://smithery.ai/badge/@OctoMind-dev/octomind-mcp)](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)\n\nOctomind предоставляет целую платформу e2e для создания, выполнения и управления тестами, включая автоматическое исправление. С этим сервером MCP вы можете использовать инструменты и ресурсы Octomind в вашей локальной среде разработки и позволить ему создавать новые тесты e2e, выполнять их и многое другое. Подробнее см. и .\n\n## Посмотрите на это в действии вместе с testrail mcp\n\n[![Название видео](https://img.youtube.com/vi/I7lc9I0S62Y/0.jpg)](https://www.youtube.com/watch?v=I7lc9I0S62Y)\n\n## Конфигурация\n\n### Переменные среды\n\nСервер использует следующие переменные среды:\n\n* `APIKEY` — API-ключ для Octomind API (обязательно)\n* `OCTOMIND_API_URL` — базовый URL-адрес для конечной точки API (по умолчанию )\n* `REDIS_URL` — URL-адрес подключения Redis для хранения сеансов (необязательно, формат: redis://host:port)\n* `SESSION_EXPIRATION_SECONDS` — время в секундах, по истечении которого сеансы истекают (необязательно, только Redis)\n\n### Параметры командной строки\n\nСервер поддерживает следующие параметры командной строки:\n\n* `-s, --sse` — Включить транспортный режим SSE\n* `-t, --stream` — включить потоковый режим HTTP-транспорта\n* `-c, --clients` — Показать примеры конфигурации клиента\n* `-p, --port ` — Порт для прослушивания (по умолчанию: 3000)\n* `-r, --redis-url ` — URL-адрес Redis для хранения сеансов\n* `-e, --session-expiration ` — Время окончания сеанса в секундах\n\n### Хранение сеансов\n\nСервер поддерживает два типа хранения сессий:\n\n1. **Хранение в памяти** (по умолчанию) — сеансы хранятся в памяти и будут потеряны при перезапуске сервера.\n2. **Хранилище Redis** — сеансы хранятся в Redis и могут сохраняться после перезапуска сервера.\n\nДля производственных развертываний рекомендуется использовать хранилище Redis с соответствующим временем истечения сеанса. Опция хранилища Redis также обеспечивает горизонтальное масштабирование с несколькими экземплярами сервера.\n\n### Конфигурация ведения журнала\n\n* `LOG_FILENAME` - Файл для записи журналов (только для отладки). Если не задано, журналирование отключено\n* `LOG_LEVEL` — используемый уровень журнала (по умолчанию — info)\n\n## Инструменты\n\nВ этом сервере MCP реализованы следующие инструменты:\n\n* `search` - Поиск документации Octomind по заданному запросу.\n* `getTestCase` — извлечение тестового случая для заданной тестовой цели и идентификатора тестового случая\n* `executeTests` — запуск выполнения теста для заданной тестовой цели по указанному URL-адресу\n* `getEnvironments` — список сред для тестового объекта\n* `createEnvironment` — создание новой среды для тестового объекта\n* `updateEnvironment` — обновить существующую среду\n* `deleteEnvironment` - Удалить среду\n* `getTestReports` — получение отчетов о тестировании для целевого объекта тестирования\n* `getTestReport` — получить конкретный отчет об испытаниях по идентификатору\n* `discovery` - создание тестового случая с описанием или подсказкой\n* `getPrivateLocations` — список всех частных местоположений, настроенных для организации\n* `getVersion` — получить текущую версию сервера Octomind MCP\n\n## Установка\n\nВы можете получить фрагменты конфигурации для разных клиентов, выполнив:\n\n```bash\nnpx @octomind/octomind-mcp --clients\n```\n\nЭто выведет примеры конфигурации для Claude Desktop, Cursor и Windsurf. Вот файлы конфигурации для большинства клиентов:\n\n### Установка через Smithery\n\nЧтобы автоматически установить octomind-mcp для Claude Desktop через [Smithery](https://smithery.ai/server/@OctoMind-dev/octomind-mcp) :\n\n```bash\nnpx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude\n```\n\n### Рабочий стол Клода (.claude-config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Курсор (cursor.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Виндсерфинг (mcp\\_config.json)\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"environment\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\nПримечание: замените `your-api-key-here` на ваш фактический ключ API.\n\nЧтобы получить APIKEY, смотрите здесь \n\n# Листинги / Интеграции\n\n[![Значок оценки безопасности MseeP.ai](https://mseep.net/pr/octomind-dev-octomind-mcp-badge.png)](https://mseep.ai/app/octomind-dev-octomind-mcp)","Russian","ru-RU",{"_34":80,"_38":84,"_43":85},{"_36":81,"_38":82,"_40":83},"mcp 服务器与 octomind 平台交互。octomind 为 e2e Web 测试提供了创建、运行和修复解决方案，请参阅[https://octomind.dev](https://octomind.dev)","八脑-MCP","# octomind mcp 服务器：让代理创建和管理 e2e 测试\n\n[![铁匠徽章](https://smithery.ai/badge/@OctoMind-dev/octomind-mcp)](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)\n\nOctomind 提供了一个完整的端到端 (e2e) 平台，用于测试创建、执行和管理，包括自动修复。借助此 MCP 服务器，您可以在本地开发环境中使用 Octomind 的工具和资源，并启用它来创建新的端到端测试、执行测试等等。更多详情，请参阅和。\n\n## 与 testrail mcp 一起查看实际运行情况\n\n[![视频标题](https://img.youtube.com/vi/I7lc9I0S62Y/0.jpg)](https://www.youtube.com/watch?v=I7lc9I0S62Y)\n\n## 配置\n\n### 环境变量\n\n服务器使用以下环境变量：\n\n* `APIKEY` - Octomind API 的 API 密钥（必需）\n* `OCTOMIND_API_URL` - 要使用的 API 端点的基本 URL（默认为）\n* `REDIS_URL` - 用于会话存储的 Redis 连接 URL（可选，格式：redis://host:port）\n* `SESSION_EXPIRATION_SECONDS` - 会话过期后的秒数（可选，仅限 Redis）\n\n### 命令行选项\n\n服务器支持以下命令行选项：\n\n* `-s, --sse` - 启用 SSE 传输模式\n* `-t, --stream` - 启用可流式传输的 HTTP 传输模式\n* `-c, --clients` - 显示客户端配置示例\n* `-p, --port ` - 监听的端口（默认值：3000）\n* `-r, --redis-url ` - 用于会话存储的 Redis URL\n* `-e, --session-expiration ` - 会话过期时间（秒）\n\n### 会话存储\n\n服务器支持两种类型的会话存储：\n\n1. **内存存储**（默认）- 会话存储在内存中，服务器重启时将丢失\n2. **Redis 存储**- 会话存储在 Redis 中，并可在服务器重启后保留\n\n对于生产部署，建议使用具有适当会话过期时间的 Redis 存储。Redis 存储选项还支持使用多个服务器实例进行水平扩展。\n\n### 日志配置\n\n* `LOG_FILENAME` - 日志写入文件（仅用于调试）。如果未设置，则禁用日志记录\n* `LOG_LEVEL` - 要使用的日志级别（默认为信息）\n\n## 工具\n\n此 MCP 服务器中实现了以下工具：\n\n* `search` - 在 Octomind 文档中搜索给定的查询\n* `getTestCase` - 检索给定测试目标和测试用例 ID 的测试用例\n* `executeTests` ——在指定的 URL 上触发给定测试目标的测试执行\n* `getEnvironments` - 列出测试目标的环境\n* `createEnvironment`为测试目标创建新环境\n* `updateEnvironment` - 更新现有环境\n* `deleteEnvironment` - 删除环境\n* `getTestReports` - 检索测试目标的测试报告\n* `getTestReport` - 根据 ID 获取特定的测试报告\n* `discovery` - 创建带有描述或提示的测试用例\n* `getPrivateLocations` - 列出为组织配置的所有私人位置\n* `getVersion` - 获取 Octomind MCP 服务器的当前版本\n\n## 安装\n\n您可以通过运行以下命令获取不同客户端的配置片段：\n\n```bash\nnpx @octomind/octomind-mcp --clients\n```\n\n这将输出 Claude Desktop、Cursor 和 Windsurf 的配置示例。以下是大多数客户端的配置文件：\n\n### 通过 Smithery 安装\n\n要通过[Smithery](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)自动为 Claude Desktop 安装 octomind-mcp：\n\n```bash\nnpx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude\n```\n\n### Claude 桌面（.claude-config.json）\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### 游标（cursor.json）\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### 风帆冲浪（mcp\\_config.json）\n\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"environment\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n注意：将`your-api-key-here`替换为您的实际 API 密钥。\n\n要获取 APIKEY，请参阅此处\n\n# 列表/集成\n\n[![MseeP.ai 安全评估徽章](https://mseep.net/pr/octomind-dev-octomind-mcp-badge.png)](https://mseep.ai/app/octomind-dev-octomind-mcp)","Chinese","zh-CN","githubUser","locale",{"_89":90,"_20":91,"_100":47,"_101":47,"_23":102,"_103":104,"_38":48,"_105":106,"_114":-5,"_115":116,"_117":118,"_176":177,"_182":-5,"_113":48,"_183":184,"_8":185,"_186":187},"addedAt","2025-03-27T18:06:58.132998Z",[92,93,94,95,96,97,98,99],"author:official","category:testing-and-qa-tools","category:browser-automation","hosting:remote-capable","language:typescript","security_grade:a","quality_grade:a","license_grade:a","descriptionMarkdown","descriptionPlainText",3993,"integrations",[],"namespace",{"_107":108,"_113":112},"owner",{"_109":110},"githubAccount",{"_111":112},"login","OctoMind-dev","slug","readmeMarkdown","redditPostExternalId","1nqskz4","repository",{"_119":120,"_142":143,"_147":148,"_167":-5,"_168":169,"_170":171,"_175":-5},"argumentsJsonSchema",{"_121":122,"_139":140,"_12":141},"properties",{"_123":124,"_127":128,"_132":133,"_135":136},"APIKEY",{"_36":125,"_12":126},"The API key for Octomind API","string","LOG_LEVEL",{"_129":130,"_36":131,"_12":126},"default","info","The log level to use","LOG_FILENAME",{"_36":134,"_12":126},"The file to write logs to (only for debugging). If not set, logging is disabled","OCTOMIND_API_URL",{"_129":137,"_36":138,"_12":126},"https://app.octomind.dev/api","Base URL for the API endpoint to use","required",[123],"object","githubProject",{"_40":144,"_145":146},"# octomind mcp server: let agents create and manage e2e tests\n\n $\"Octomind$ \n\n[![smithery badge](https://smithery.ai/badge/@OctoMind-dev/octomind-mcp)](https://smithery.ai/server/@OctoMind-dev/octomind-mcp)\n\nOctomind provides a whole e2e platform for test creation, execution and management including auto-fix.\nWith this MCP server you can use Octomind tools and resources in your local development environment and \nenable it to create new e2e tests, execute them and more. see https://octomind.dev/ and \nhttps://octomind.dev/docs/mcp/install-octomind-mcp for more details.\n\n## See it in action together with testrail mcp\n\n[![Video Title](https://img.youtube.com/vi/I7lc9I0S62Y/0.jpg)](https://www.youtube.com/watch?v=I7lc9I0S62Y)\n\n## Configuration\n\n### Environment Variables\n\nThe server uses the following environment variables:\n\n- `APIKEY` - The API key for Octomind API (required)\n- `OCTOMIND_API_URL` - Base URL for the API endpoint to use (defaults to https://app.octomind.dev/api)\n- `REDIS_URL` - Redis connection URL for session storage (optional, format: redis://host:port)\n- `SESSION_EXPIRATION_SECONDS` - Time in seconds after which sessions expire (optional, Redis only)\n\n### Command Line Options\n\nThe server supports the following command line options:\n\n- `-s, --sse` - Enable SSE transport mode\n- `-t, --stream` - Enable Streamable HTTP transport mode\n- `-c, --clients` - Show client configuration examples\n- `-p, --port ` - Port to listen on (default: 3000)\n- `-r, --redis-url ` - Redis URL for session storage\n- `-e, --session-expiration ` - Session expiration time in seconds\n\n### Session Storage\n\nThe server supports two types of session storage:\n\n1. **In-memory storage** (default) - Sessions are stored in memory and will be lost when the server restarts\n2. **Redis storage** - Sessions are stored in Redis and can persist across server restarts\n\nFor 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.\n\n### Logging Configuration\n\n- `LOG_FILENAME` - The file to write logs to (only for debugging). If not set, logging is disabled\n- `LOG_LEVEL` - The log level to use (defaults to info)\n\n## Tools\n\nThe following tools are implemented in this MCP server:\n\n- `search` - Search the Octomind documentation for a given query\n- `getTestCase` - Retrieve a test case for a given test target and test case ID\n- `executeTests` - Trigger test execution for a given test target on a specified URL\n- `getEnvironments` - List environments for a test target\n- `createEnvironment` - Create a new environment for a test target\n- `updateEnvironment` - Update an existing environment\n- `deleteEnvironment` - Delete an environment\n- `getTestReports` - Retrieve test reports for a test target\n- `getTestReport` - Get a specific test report by ID\n- `discovery` - Create a test case with a description or prompt\n- `getPrivateLocations` - List all private locations configured for the organization\n- `getVersion` - Get the current version of the Octomind MCP server\n\n## Installation\n\nYou can get configuration snippets for different clients by running:\n\n```bash\nnpx @octomind/octomind-mcp --clients\n```\n\nThis will output configuration examples for Claude Desktop, Cursor, and Windsurf. Here are the configuration files for most clients:\n\n### Installing via Smithery\n\nTo install octomind-mcp for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@OctoMind-dev/octomind-mcp):\n\n```bash\nnpx -y @smithery/cli install @OctoMind-dev/octomind-mcp --client claude\n```\n\n### Claude Desktop (.claude-config.json)\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Cursor (cursor.json)\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"env\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\n### Windsurf (mcp_config.json)\n```json\n{\n \"mcpServers\": {\n \"octomind-mcp\": {\n \"name\": \"Octomind MCP Server\",\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@octomind/octomind-mcp@latest\"\n ],\n \"environment\": {\n \"APIKEY\": \"your-api-key-here\"\n }\n }\n }\n}\n```\n\nNote: Replace `your-api-key-here` with your actual API key.\n\nTo get an APIKEY see here https://octomind.dev/docs/get-started/execution-without-ci#create-an-api-key\n\n# Listings / Integrations\n\nCertified by [MCPHub](https://mcphub.com/mcp-servers/octomind-dev/octomind-mcp)\n\n\n $\"octomind-mcp$ \n\n\n[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/octomind-dev-octomind-mcp-badge.png)](https://mseep.ai/app/octomind-dev-octomind-mcp)\n\n","url","https://github.com/OctoMind-dev/octomind-mcp","githubRepository",{"_149":150,"_151":152,"_153":154,"_23":155,"_156":157,"_38":48,"_107":158,"_160":161,"_162":163,"_165":166},"defaultBranch","main","fullName","OctoMind-dev/octomind-mcp","githubTreeId",1694607,6727,"language","TypeScript",{"_111":112,"_8":159},"vdKjExVd58","recentStargazers",0,"spdxLicense",{"_38":164},"MIT License","stargazers",21,"glamaJson","inspectable",true,"npmPackage",{"_38":172,"_173":174},"@octomind/octomind-mcp","weeklyDownloads",698,"supportedPlatforms","scores",{"_178":179,"_180":179,"_181":179},"license",100,"quality","security","simpleIcon","toolCount",16,"jr7wdry856","updatedAt","2025-10-06T15:25:40.210237Z","meta",[190,192,194,201,204,206,209,212,215,218,221,223,226,229,231,233,235,237,239],{"_10":191},"octomind-mcp | Glama",{"_193":47,"_38":36},"content",{"_195":196,"_197":198,"_199":200},"href","https://glama.ai/mcp/servers/@OctoMind-dev/octomind-mcp","rel","canonical","tagName","link",{"_193":48,"_202":203},"property","og:title",{"_193":47,"_202":205},"og:description",{"_193":207,"_202":208},"https://glama.ai/logo.png","og:logo",{"_193":210,"_202":211},"https://glama.ai/mcp/servers/@OctoMind-dev/octomind-mcp/og-image","og:image",{"_193":213,"_202":214},"630","og:image:height",{"_193":216,"_202":217},"1200","og:image:width",{"_193":219,"_202":220},"website","og:type",{"_193":196,"_202":222},"og:url",{"_193":224,"_202":225},"Glama – MCP Hosting Platform","og:site_name",{"_193":227,"_38":228},"summary_large_image","twitter:card",{"_193":224,"_38":230},"twitter:title",{"_193":47,"_38":232},"twitter:description",{"_193":210,"_38":234},"twitter:image",{"_193":213,"_38":236},"twitter:image:height",{"_193":216,"_38":238},"twitter:image:width",{"_240":241},"script:ld+json",{"_242":243,"_244":245},"@context","http://schema.org","@graph",[246],{"_242":247,"_248":249,"_250":251},"https://schema.org","@type","BreadcrumbList","itemListElement",[252,259,263,267],{"_248":253,"_254":255,"_38":256,"_257":258},"ListItem","item","/","Glama","position",1,{"_248":253,"_254":260,"_38":261,"_257":262},"/mcp","MCP",2,{"_248":253,"_254":264,"_38":265,"_257":266},"/mcp/servers","Servers",3,{"_248":253,"_254":268,"_38":48,"_257":269},"/mcp/servers/@OctoMind-dev/octomind-mcp",4,"visitorIsMaintainer",false,"routes/_public/mcp/servers/~namespace/~slug/_pages/_explorer/blob/~commit/~/_route",{"_274":275,"_34":281,"_301":302,"_188":315,"_313":339,"_340":341},"blob",{"_193":276,"_277":278,"_279":280},"\n","fileName","light.svg","size",13884,{"_89":90,"_20":282,"_100":47,"_101":47,"_23":102,"_103":283,"_38":48,"_105":284,"_114":-5,"_115":116,"_117":287,"_176":300,"_182":-5,"_113":48,"_183":184,"_8":185,"_186":187},[92,93,94,95,96,97,98,99],[],{"_107":285,"_113":112},{"_109":286},{"_111":112},{"_119":288,"_142":295,"_147":296,"_167":-5,"_168":169,"_170":299,"_175":-5},{"_121":289,"_139":294,"_12":141},{"_123":290,"_127":291,"_132":292,"_135":293},{"_36":125,"_12":126},{"_129":130,"_36":131,"_12":126},{"_36":134,"_12":126},{"_129":137,"_36":138,"_12":126},[123],{"_40":144,"_145":146},{"_149":150,"_151":152,"_153":154,"_23":155,"_156":157,"_38":48,"_107":297,"_160":161,"_162":298,"_165":166},{"_111":112,"_8":159},{"_38":164},{"_38":172,"_173":174},{"_178":179,"_180":179,"_181":179},"member",{"_303":304,"_307":308,"_309":310,"_153":311,"_312":271,"_313":278,"_314":169,"_279":280,"_12":274},"commit",{"_305":306},"sha","ccd539d3968d6e1d6d0deafd642176254447be41","contentStoredObjectPointerId",10632264,"fullPath","images/light.svg",1694602,"indexable","path","safeToDisplayAsText",[316,318,320,322,324,325,326,328,329,330,331,332,333,334,335,336,337,338],{"_10":317},"light.svg | octomind-mcp | Glama",{"_193":319,"_38":36},"Enterprise-grade security, privacy, and features like agents, MCP, prompt templates, and more.",{"_195":321,"_197":198,"_199":200},"https://glama.ai/mcp/servers/@OctoMind-dev/octomind-mcp/blob/ccd539d3968d6e1d6d0deafd642176254447be41/images",{"_193":323,"_202":203},"light.svg | octomind-mcp",{"_193":319,"_202":205},{"_193":207,"_202":208},{"_193":327,"_202":211},"https://glama.ai/generated-images/og?title=light.svg+%7C+octomind-mcp",{"_193":213,"_202":214},{"_193":216,"_202":217},{"_193":219,"_202":220},{"_193":321,"_202":222},{"_193":224,"_202":225},{"_193":227,"_38":228},{"_193":224,"_38":230},{"_193":319,"_38":232},{"_193":327,"_38":234},{"_193":213,"_38":236},{"_193":216,"_38":238},"images","treeMembers",[342,346],{"_303":343,"_309":344,"_313":345,"_12":274},{"_305":306},"images/light.png","light.png",{"_303":347,"_309":310,"_313":278,"_12":274},{"_305":306},"actionData","errors"]

MCP directory API