christmas-mcp-copilot-runner/VSCODE_UI_FIX_GUIDE.md

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

# VS Code MCP Configuration Troubleshooting

## 🚨 Critical Issue: VS Code UI Defaults to NPX

The VS Code "Add Server..." UI has a known issue where it automatically defaults to `npx` command instead of `node`. This causes performance issues and version conflicts.

### ❌ The Problem

When you use VS Code's MCP settings UI to add christmas-mcp-copilot-runner, it creates:

```json
{
  "command": "npx",
  "args": ["christmas-mcp-copilot-runner", "--mcp"]
}
```

This is **WRONG** and causes:
- ⚠️ Slow startup times (package resolution overhead)
- ⚠️ Potential version conflicts  
- ⚠️ Network dependency for every startup
- ⚠️ Unreliable performance

### ✅ The Solution

Use **our automatic setup script** which creates the correct configuration:

```json
{
  "command": "node",
  "args": ["/path/to/christmas-mcp-copilot-runner/src/index.js", "--mcp"]
}
```

This provides:
- ✅ Fast startup (direct execution)
- ✅ Consistent performance
- ✅ No network dependencies
- ✅ Reliable operation

## 🔧 How to Fix Wrong Configuration

### Method 1: Use Our Setup Script (Recommended)

```bash
npm install -g christmas-mcp-copilot-runner
mcp-setup-vscode
```

The setup script will:
1. Detect your npm installation path
2. Create correct VS Code configuration
3. Set up auto-approval
4. Configure all settings properly

### Method 2: Manual Fix in VS Code

1. Open VS Code Settings (Cmd/Ctrl + ,)
2. Search for "mcp"
3. Find "MCP: Servers" section
4. Click "Edit in settings.json"
5. Find your christmas-mcp-copilot-runner entry
6. Change the configuration:

**Change this (WRONG):**
```json
"mcp.servers": {
  "christmas-mcp-copilot-runner": {
    "command": "npx",
    "args": ["christmas-mcp-copilot-runner", "--mcp"]
  }
}
```

**To this (CORRECT):**
```json
"mcp.servers": {
  "christmas-mcp-copilot-runner": {
    "command": "node",
    "args": ["/usr/local/lib/node_modules/christmas-mcp-copilot-runner/src/index.js", "--mcp"],
    "alwaysAllow": true
  }
}
```

### Method 3: Delete and Recreate

1. In VS Code MCP settings, delete the christmas-mcp-copilot-runner server
2. **DO NOT** use "Add Server..." button
3. Run our setup script: `mcp-setup-vscode`

## 🔍 How to Find Your Correct Path

Run this command to find your npm global installation:

```bash
npm list -g christmas-mcp-copilot-runner
```

Common paths:
- **macOS:** `/usr/local/lib/node_modules/christmas-mcp-copilot-runner/src/index.js`
- **Windows:** `%APPDATA%\npm\node_modules\christmas-mcp-copilot-runner\src\index.js`
- **Linux:** `/usr/local/lib/node_modules/christmas-mcp-copilot-runner/src/index.js`

## 🧪 Testing Your Configuration

1. Restart VS Code completely (Cmd+Q or Ctrl+Q then reopen)
2. Open a workspace
3. Ask GitHub Copilot: "Use christmas-mcp-copilot-runner to run ls"
4. Check startup time and performance

### Good Performance Indicators:
- ✅ Commands execute in under 1 second
- ✅ No "resolving package" messages
- ✅ Consistent response times

### Bad Performance Indicators:
- ❌ Long delays before execution (3+ seconds)
- ❌ "npm WARN" or resolution messages
- ❌ Inconsistent performance

## 🚨 Never Use VS Code "Add Server..." UI

The VS Code MCP extension UI is broken for npm packages. It will always default to `npx` which is the wrong configuration.

**Always use our setup script instead:**

```bash
mcp-setup-vscode
```

## 📞 Still Having Issues?

1. Check our [troubleshooting guide](./VSCODE_TROUBLESHOOTING.md)
2. Verify your npm installation: `npm list -g christmas-mcp-copilot-runner`
3. Test manually: `christmas-mcp-copilot-runner --mcp`
4. Open an issue on our [GitHub repository](https://github.com/Chr1stm4s/christmas-mcp-copilot-bypass)

## 📝 Summary

- ❌ **Never** use VS Code "Add Server..." UI for christmas-mcp-copilot-runner
- ✅ **Always** use our setup script: `mcp-setup-vscode`  
- ✅ **Ensure** your configuration uses `"command": "node"`
- ✅ **Verify** direct path to src/index.js in args
- ✅ **Restart** VS Code completely after configuration changes