@aiwerk/mcp-bridge 2.7.1 → 2.7.2

package/dist/src/transport-stdio.js

@@ -153,15 +153,12 @@ export class StdioTransport extends BaseTransport {
             this.process.once("error", onProcessError);
             this.process.once("exit", onProcessExit);
             timeout = setTimeout(() => {
-                const timeoutError = new Error(`Stdio process startup timeout: no data received within ${connectionTimeout}ms`);
-                this.logger.warn(`[mcp-bridge] ${timeoutError.message}; terminating unresponsive process`);
-                try {
-                    this.process?.kill("SIGTERM");
-                }
-                catch {
-                    // Ignore kill errors and reject with timeout
-                }
-                settleReject(timeoutError);
+                // Many MCP servers (e.g. firecrawl) don't write anything to stdout until
+                // they receive the client's `initialize` request. Instead of killing the
+                // process, resolve optimistically — initializeProtocol() will validate
+                // the connection by sending `initialize` and waiting for a response.
+                this.logger.info(`[mcp-bridge] No stdout data within ${connectionTimeout}ms — process still running, proceeding to initialize`);
+                settleResolve();
             }, connectionTimeout);
         });
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aiwerk/mcp-bridge",
-  "version": "2.7.1",
+  "version": "2.7.2",
   "description": "Standalone MCP server that multiplexes multiple MCP servers into one interface",
   "type": "module",
   "main": "./dist/src/index.js",