christmas-mcp-copilot-runner/WINDOWS_VS_CODE_FIX.md

A Model Copilot Provider (MCP) for safely executing whitelisted system commands across platforms with automatic VS Code setup

# Windows VS Code MCP Configuration Fix

## 🚨 Problem: Windows VS Code Shows Complex Configuration

If you see this complex configuration on Windows instead of simple direct execution:

```json
"christmas-mcp-copilot-runner-nuc": {
    "tool_uses": [
        {
            "recipient_name": "functions.getInput",
            // ... complex wizard configuration
        }
    ],
    "type": "stdio"
}
```

**This is WRONG!** You need the simple direct configuration like macOS.

## ✅ Windows Fix: Manual Configuration

### Step 1: Remove the Complex Configuration

1. Open VS Code Settings (Ctrl+,)
2. Search for "mcp"  
3. Find "MCP: Servers" section
4. Click "Edit in settings.json"
5. **DELETE** the entire `christmas-mcp-copilot-runner-nuc` entry with `tool_uses`

### Step 2: Add the Correct Simple Configuration

Replace it with this **EXACT** configuration:

```json
{
  "mcp.servers": {
    "christmas-mcp-copilot-runner": {
      "command": "node",
      "args": [
        "C:\\Users\\YourUsername\\AppData\\Roaming\\npm\\node_modules\\christmas-mcp-copilot-runner\\src\\index.js",
        "--mcp"
      ],
      "cwd": "C:\\Your\\Project\\Directory",
      "env": {},
      "disabled": false,
      "alwaysAllow": true
    }
  },
  "languageModels.experimental": {
    "tools": {
      "enabled": true,
      "autoApprove": ["christmas-mcp-copilot-runner"]
    }
  },
  "github.copilot.enable": {
    "*": true
  },
  "workbench.trust.enabled": false
}
```

### Step 3: Find Your Windows Paths

**Find your npm global path:**
```cmd
npm list -g christmas-mcp-copilot-runner
```

**Common Windows paths:**
- `C:\\Users\\YourUsername\\AppData\\Roaming\\npm\\node_modules\\christmas-mcp-copilot-runner\\src\\index.js`
- `C:\\Program Files\\nodejs\\node_modules\\christmas-mcp-copilot-runner\\src\\index.js`

**Set your project directory:**
- Replace `"cwd": "C:\\Your\\Project\\Directory"` with your actual project path
- Example: `"cwd": "C:\\Projects\\gear-garage\\www"`

### Step 4: Windows-Specific Notes

1. **Use double backslashes**: `\\` in Windows paths (JSON escaping)
2. **Use absolute paths**: Full C:\\ paths, not relative paths  
3. **Check your username**: Replace `YourUsername` with your actual Windows username
4. **Restart VS Code completely**: Close all windows, then reopen

## 🧪 Test Your Windows Configuration

After setup, test with GitHub Copilot:
```
"Use christmas-mcp-copilot-runner to run dir"
"Use christmas-mcp-copilot-runner to run cd C:\Projects\myproject && php -l file.php"
```

## 🚨 Why This Happens on Windows

1. **Different MCP Extension Behavior**: Windows VS Code MCP extension may default to complex wizard mode
2. **NPM Path Differences**: Windows npm global installation paths are different
3. **Add Server UI Bug**: If you used "Add Server..." button, it creates the wrong configuration

## ✅ Prevention

- **Never use "Add Server..." UI** on any platform
- **Always use direct manual configuration** for Windows
- **Use our automatic setup script when available** (works better on macOS/Linux)

## 📞 Still Having Issues?

If the manual configuration doesn't work:

1. **Verify npm installation**: `npm list -g christmas-mcp-copilot-runner`  
2. **Check exact path**: Navigate to the path in Windows Explorer
3. **Test manually**: `node "C:\path\to\index.js" --mcp`
4. **Check VS Code extensions**: Ensure MCP extensions are installed and enabled

The key is getting the **simple direct node execution** instead of the complex `tool_uses` wizard configuration!