@tgai96/outlook-mcp 1.0.0 → 1.0.1

package/README.md

@@ -136,17 +136,7 @@ To use this MCP server with an MCP client, you can either use the published npm
 If the package is published to npm, you can use it directly:
 
 ```json
-{
-  "mcpServers": {
-    "outlook": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@yourusername/outlook-mcp"
-      ]
-    }
-  }
-}
+DDD
 ```
 
 **Note**: The package name is `@tgai96/outlook-mcp` once published.

package/cli.js

@@ -216,31 +216,12 @@ if (command === 'config') {
     process.exit(1);
   });
 } else {
-  // Default: Start the MCP server
+  // Default: Start the MCP server directly (not as child process)
   // This is what gets run when npx outlook-mcp is called without arguments
+  // We need to run index.js directly (not spawn) for proper stdio communication with MCP clients
   const mcpServerPath = path.join(__dirname, 'index.js');
-  const child = spawn('node', [mcpServerPath], {
-    stdio: 'inherit',
-    env: process.env
-  });
   
-  // Handle process termination
-  process.on('SIGINT', () => {
-    child.kill('SIGINT');
-    process.exit(0);
-  });
-  
-  process.on('SIGTERM', () => {
-    child.kill('SIGTERM');
-    process.exit(0);
-  });
-  
-  child.on('exit', (code) => {
-    process.exit(code || 0);
-  });
-  
-  child.on('error', (error) => {
-    console.error('Error starting MCP server:', error.message);
-    process.exit(1);
-  });
+  // For MCP server mode, we need direct stdio, so require and run index.js directly
+  // This ensures proper communication with MCP clients
+  require(mcpServerPath);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tgai96/outlook-mcp",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "MCP server for Claude to access Outlook data via Microsoft Graph API",
   "main": "index.js",
   "bin": {