@dynamicu/chromedebug-mcp 2.4.2 → 2.4.4

package/README.md

@@ -36,19 +36,56 @@ npm install
 claude mcp add chromedebug -s user -- chromedebug-mcp
 ```
 
+The MCP server will automatically start both the stdio MCP server and HTTP server for Chrome extension integration.
+
 #### Windows
 
-On Windows, use `cmd /c` to properly execute the server:
+On Windows, the MCP server and HTTP server should be run separately for best reliability:
 
+**Step 1: Add MCP Server for Claude Code**
 ```bash
 claude mcp add chromedebug -s user -- cmd /c chromedebug-mcp
 ```
 
-**Note for Windows Users:** Process cleanup is currently limited on Windows. The server will start successfully but won't clean up orphaned processes from previous sessions. A full cross-platform process management solution is planned for a future release.
+**Step 2: Start HTTP Server for Chrome Extension (separate terminal)**
+```bash
+chromedebug-mcp-server
+```
+
+**Why Separate?** On Windows, the stdio-based MCP server (for Claude Code) works best when running independently from the HTTP server (for Chrome extension). This separation provides better stability and prevents connection issues.
+
+**Note for Windows Users:**
+- Process cleanup is currently limited on Windows. The server will start successfully but won't clean up orphaned processes from previous sessions.
+- If you only need Claude Code integration (no Chrome extension), the MCP server alone is sufficient.
+- If you need the Chrome extension, run both servers in separate terminal windows.
+
+### Standalone HTTP Server (New in v2.4.3)
+
+For Windows users or those who prefer to run services separately, you can start the HTTP server independently:
+
+```bash
+# Start HTTP server only (no MCP)
+chromedebug-mcp-server
+
+# With options
+chromedebug-mcp-server --verbose --port 3000
+```
+
+**Available Options:**
+- `--port PORT` - Specify HTTP server port (optional, auto-discovers if not set)
+- `--verbose` - Enable verbose logging
+- `--debug` - Enable debug mode
+- `--no-cleanup` - Skip process cleanup on startup
+- `--session-id ID` - Set custom session ID
+
+**Use Cases:**
+- Windows users who want Chrome extension support without running full MCP server
+- Development environments where you want HTTP server running persistently
+- Situations where MCP and HTTP servers should run in separate processes
 
 ### Embedded HTTP Server
 
-Chrome Debug automatically starts an embedded HTTP server for Chrome extension communication. The server uses ports configured in `config/chrome-pilot-config.json` (default: 3001, 3000, 3002, 3028). The server provides these REST API endpoints:
+Chrome Debug can automatically start an embedded HTTP server for Chrome extension communication. The server uses ports configured in `config/chrome-pilot-config.json` (default: 3001, 3000, 3002, 3028). The server provides these REST API endpoints:
 
 | Endpoint | Method | Description | Body |
 |----------|--------|-------------|------|

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@dynamicu/chromedebug-mcp",
-  "version": "2.4.2",
+  "version": "2.4.4",
   "description": "ChromeDebug MCP - MCP server that provides full control over a Chrome browser instance for debugging and automation with AI assistants like Claude Code",
   "main": "src/index.js",
   "type": "module",
   "bin": {
-    "chromedebug-mcp": "./src/cli.js"
+    "chromedebug-mcp": "./src/cli.js",
+    "chromedebug-mcp-server": "./src/standalone-server.js"
   },
   "publishConfig": {
     "access": "public"

package/src/services/chrome-service.js

@@ -26,11 +26,13 @@ export class ChromeService {
 
   /**
    * Initializes the Chrome service with HTTP server if needed
+   * Windows-specific: HTTP server failures are non-fatal to prevent MCP crashes
    * @param {Object} options - Initialization options
    * @returns {Promise<Object>} Initialization result
    */
   async initialize(options = {}) {
     const { startHttp = true, singleServer = false, sessionManager = null } = options;
+    const isWindows = process.platform === 'win32';
 
     const result = {
       chromeService: 'initialized',
@@ -57,7 +59,16 @@ export class ChromeService {
           console.error('Falling back to port discovery');
         }
 
-        const { httpServer, serverPort } = await startHttpServer(this.chromeController, targetPort);
+        // Platform-specific timeout: Windows needs longer initialization time
+        const httpTimeout = isWindows ? 20000 : 10000;
+
+        // Start HTTP server with timeout protection
+        const httpServerPromise = startHttpServer(this.chromeController, targetPort);
+        const timeoutPromise = new Promise((_, reject) =>
+          setTimeout(() => reject(new Error(`HTTP server startup timeout after ${httpTimeout}ms`)), httpTimeout)
+        );
+
+        const { httpServer, serverPort } = await Promise.race([httpServerPromise, timeoutPromise]);
 
         this.httpServer = httpServer;
         this.httpServerPort = serverPort;
@@ -69,11 +80,25 @@ export class ChromeService {
 
         console.error(`HTTP server started on port ${serverPort}`);
       } catch (error) {
-        console.error('Failed to start HTTP server:', error);
+        // IMPORTANT: HTTP server failures are non-fatal
+        // This prevents MCP server crashes when HTTP server can't start
+        const errorMessage = error.message || String(error);
+        console.error('⚠️  HTTP Server Initialization Failed (non-fatal):', errorMessage);
+
+        if (isWindows) {
+          console.error('ℹ️  On Windows, you can start the HTTP server separately:');
+          console.error('   npm run server');
+          console.error('   or: chromedebug-mcp-server');
+        }
+
         result.httpServer = {
-          error: error.message,
-          status: 'failed'
+          error: errorMessage,
+          status: 'failed',
+          platform: process.platform,
+          fatal: false // Explicitly mark as non-fatal
         };
+
+        // Do NOT throw - allow MCP server to continue without HTTP
       }
     }