Skip to content

Commit 4d20604

Browse files
committed
Avoid importing PowerShell.MCP in test script by using direct proxy path
1 parent f23a25c commit 4d20604

1 file changed

Lines changed: 10 additions & 2 deletions

File tree

.github/workflows/cross-platform-test.yml

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -367,9 +367,17 @@ jobs:
367367
throw "Named Pipe server did not start within 15 seconds"
368368
}
369369
370-
# Start Proxy
370+
# Start Proxy (don't call Get-MCPProxyPath to avoid importing module in test script)
371371
Write-Host "Starting Proxy..."
372-
$proxyPath = Get-MCPProxyPath
372+
# Build proxy path directly to avoid loading PowerShell.MCP in test script
373+
if ($IsWindows) {
374+
$proxyPath = "$env:USERPROFILE\Documents\PowerShell\Modules\PowerShell.MCP\bin\win-x64\PowerShell.MCP.Proxy.exe"
375+
} elseif ($IsMacOS) {
376+
$proxyPath = "$HOME/.local/share/powershell/Modules/PowerShell.MCP/bin/osx-arm64/PowerShell.MCP.Proxy"
377+
} else {
378+
$proxyPath = "$HOME/.local/share/powershell/Modules/PowerShell.MCP/bin/linux-x64/PowerShell.MCP.Proxy"
379+
}
380+
Write-Host "Proxy path: $proxyPath"
373381
$psi = [System.Diagnostics.ProcessStartInfo]::new()
374382
$psi.FileName = $proxyPath
375383
$psi.RedirectStandardInput = $true

0 commit comments

Comments
 (0)