nathan/nexus-mcp
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Tested local setup instructions.

Browse Source
This commit is contained in:
nathan 2026-04-03 14:24:28 -04:00
parent 145711e3ca
commit 4ad78b57b1
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Local Setup.md
View File

@ -26,7 +26,7 @@ Why: this starts the Inspector UI and spawns the MCP server over STDIO. If start
If you see `Proxy Server PORT IS IN USE at port 6277`, use one of the following: If you see `Proxy Server PORT IS IN USE at port 6277`, use one of the following:
PowerShell (recommended): PowerShell terminal (recommended):
```powershell ```powershell
Get-NetTCPConnection -State Listen -LocalPort 6277,6274 | Get-NetTCPConnection -State Listen -LocalPort 6277,6274 |
@ -35,19 +35,19 @@ Get-NetTCPConnection -State Listen -LocalPort 6277,6274 |
Stop-Process -Id <PID> -Force Stop-Process -Id <PID> -Force
``` ```
Important: `<PID>` is a placeholder. Replace it with a real numeric process ID from the first command.
Why: kill by PID is more reliable than killing `node.exe` by name because the owning process may vary. Why: kill by PID is more reliable than killing `node.exe` by name because the owning process may vary.
Git Bash alternative: Git Bash alternative:
```bash ```bash
for p in 6277 6274; do cd Workday/workday-mcp
pids=$(netstat -ano | awk -v port=":$p" '$2 ~ port {print $5}' | tr -d '\r' | sort -u) powershell -NoProfile -Command '$ports = 6277,6274; $conns = Get-NetTCPConnection -State Listen -ErrorAction SilentlyContinue | Where-Object { $ports -contains $_.LocalPort }; $conns | ForEach-Object { Stop-Process -Id $_.OwningProcess -Force -ErrorAction SilentlyContinue }; "cleanup-done"'
for pid in $pids; do
cmd.exe /c taskkill /F /PID "$pid"
done
done
``` ```
Why: this runs PowerShell networking commands from Git Bash in one copy/paste-safe command.
## 5. Optional quick health checks after connect ## 5. Optional quick health checks after connect
Run these tools in Inspector and verify non-empty output: Run these tools in Inspector and verify non-empty output: