fix: call startMcpServer explicitly from CLI to fix npx bundling issue (#237)

Author: mrsimpson

packages/cli/src/index.ts

@@ -19,11 +19,13 @@ if (args.length === 0) {
   // No arguments, start MCP server
   const isLocal = existsSync(join(__dirname, '../../mcp-server/dist/index.js'));
   if (isLocal) {
-    import('../../mcp-server/dist/index.js');
+    const { startMcpServer } = await import('../../mcp-server/dist/index.js');
+    await startMcpServer();
   } else {
     // Use string literal to avoid TypeScript resolution issues
     const mcpServerModule = '@codemcp/workflows-server';
-    import(mcpServerModule);
+    const { startMcpServer } = await import(mcpServerModule);
+    await startMcpServer();
   }
 } else {
   // Any arguments, run CLI

packages/mcp-server/src/index.ts

@@ -78,11 +78,14 @@ async function main() {
   }
 }
 
+// Export for explicit invocation by the CLI wrapper
+export { main as startMcpServer };
+
 // Start the server if this file is run directly
 // More robust check that works with npx and direct execution
 const isMainModule =
   import.meta.url === `file://${process.argv[1]}` ||
-  process.argv[1]?.endsWith('@codemcp/workflows-server') ||
+  process.argv[1]?.endsWith('ade-workflows-server') ||
   process.argv[1]?.endsWith('index.js');
 
 if (isMainModule) {