vme-mcp-server 0.1.8 → 0.1.9

package/dist/README.md

@@ -1,6 +1,6 @@
 # VME MCP Server
 
-Transform VMware infrastructure management into conversational AI interactions with Claude.
+Transform HPE VM Essentials infrastructure management into conversational AI interactions with Claude.
 
 ## Installation
 
@@ -15,8 +15,8 @@ npm install -g vme-mcp-server
 Create a `.env` file:
 
 ```bash
-# VMware Configuration
-VME_API_BASE_URL=https://your-vme-instance.com/api
+# HPE VM Essentials Configuration
+VME_API_BASE_URL=https://your-hpe-vme-instance.com/api
 VME_API_TOKEN=your-bearer-token
 
 # Privacy Controls (Optional)
@@ -72,7 +72,7 @@ Restart Claude Desktop. You should see the VME MCP Server tools available.
 ## Features
 
 ### Intelligent Resource Discovery
-- Unified API consolidating multiple VMware endpoints
+- Unified API consolidating multiple HPE VM Essentials endpoints
 - Intent-aware responses based on context
 - Semantic organization of compute vs infrastructure resources
 
@@ -90,11 +90,44 @@ Restart Claude Desktop. You should see the VME MCP Server tools available.
 
 ## Configuration
 
+### Environment Variable Loading (Global Install Support)
+
+The server automatically searches for `.env` files in multiple locations:
+
+1. **Current directory**: `./env` (for local development)
+2. **Home directory**: `~/.env` (for global installs)
+3. **Config directory**: `~/.config/vme-mcp-server/.env`
+4. **Documents folder**: `~/Documents/.env.vme-mcp-server`
+
+### Recommended Configuration Methods
+
+**Method 1: Direct Environment Variables (Best for Global Install)**
+
+Add to your Claude Desktop config (`~/.config/claude-desktop/config.json`):
+
+```json
+{
+  "mcpServers": {
+    "vme-mcp-server": {
+      "command": "vme-mcp-server",
+      "env": {
+        "VME_API_BASE_URL": "https://your-hpe-vme-instance.com/api",
+        "VME_API_TOKEN": "your-bearer-token"
+      }
+    }
+  }
+}
+```
+
+**Method 2: .env File (Good for Local Development)**
+
+Create `.env` file in any of the supported locations above.
+
 ### Required Environment Variables
 
 | Variable | Description | Example |
 |----------|-------------|---------|
-| `VME_API_BASE_URL` | VMware vCenter API endpoint | `https://vcenter.company.com/api` |
+| `VME_API_BASE_URL` | HPE VM Essentials API endpoint | `https://vme.company.com/api` |
 | `VME_API_TOKEN` | Bearer token for authentication | `your-bearer-token` |
 
 ### Optional Environment Variables
@@ -117,10 +150,10 @@ Restart Claude Desktop. You should see the VME MCP Server tools available.
 **"API connection failed"**
 - Verify `VME_API_BASE_URL` is correct and accessible
 - Check that `VME_API_TOKEN` has sufficient permissions
-- Ensure network connectivity to VMware infrastructure
+- Ensure network connectivity to HPE VM Essentials infrastructure
 
 **"VM creation failed"**
-- Verify user permissions in VMware for VM creation
+- Verify user permissions in HPE VM Essentials for VM creation
 - Check that specified service plans and templates exist
 - Ensure target group/zone has available resources
 
@@ -128,7 +161,7 @@ Restart Claude Desktop. You should see the VME MCP Server tools available.
 
 - Check the `.env.example` file for configuration templates
 - Review error messages for specific guidance
-- Ensure VMware infrastructure is accessible and properly configured
+- Ensure HPE VM Essentials infrastructure is accessible and properly configured
 
 ## Architecture
 
@@ -143,6 +176,6 @@ Built with TypeScript and the Model Context Protocol for seamless Claude integra
 
 ## Version
 
-Current version: 0.1.5
+Current version: 0.1.9
 
 For development documentation and contribution guidelines, see the project repository.

package/dist/server.js

@@ -9,15 +9,41 @@ const index_js_1 = require("@modelcontextprotocol/sdk/server/index.js");
 const stdio_js_1 = require("@modelcontextprotocol/sdk/server/stdio.js");
 const types_js_1 = require("@modelcontextprotocol/sdk/types.js");
 const dotenv_1 = __importDefault(require("dotenv"));
+const fs_1 = require("fs");
+const path_1 = require("path");
+const os_1 = require("os");
 const index_js_2 = require("./tools/index.js");
-// Load environment variables
-dotenv_1.default.config();
+// Load environment variables from multiple locations for global install support
+function loadEnvironmentConfig() {
+    // Priority order for .env file locations:
+    const envPaths = [
+        // 1. Current working directory (for local development)
+        (0, path_1.join)(process.cwd(), '.env'),
+        // 2. Home directory (for global installs)
+        (0, path_1.join)((0, os_1.homedir)(), '.env'),
+        // 3. XDG config directory (Linux/Mac standard)
+        (0, path_1.join)((0, os_1.homedir)(), '.config', 'vme-mcp-server', '.env'),
+        // 4. User's Documents folder (Windows-friendly)
+        (0, path_1.join)((0, os_1.homedir)(), 'Documents', '.env.vme-mcp-server')
+    ];
+    // Try to load .env from the first available location
+    for (const envPath of envPaths) {
+        if ((0, fs_1.existsSync)(envPath)) {
+            dotenv_1.default.config({ path: envPath });
+            console.error(`VME MCP: Loaded config from ${envPath}`);
+            return;
+        }
+    }
+    // If no .env file found, that's okay - environment variables may be set directly
+    console.error('VME MCP: No .env file found, using direct environment variables');
+}
+loadEnvironmentConfig();
 // Disable TLS verification for VME API (if needed)
 process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0';
 // Create VME MCP server with modular architecture
 const server = new index_js_1.Server({
     name: "vme-mcp-server",
-    version: "1.5.0",
+    version: "0.1.9",
 }, {
     capabilities: {
         tools: {},

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vme-mcp-server",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "",
   "main": "dist/server.js",
   "bin": {