Set up a computer
Install the broker once on each computer your agents use. It keeps your secrets, so your agents never see them.
On this page
Before you start
- An administrator account on that computer.
- Node.js 22.23.4, 24.22.1 or 26.12.1 or newer (not 23 or 25), from nodejs.org: older ones lack a security fix, and the helper app won't start on them.
Step 1: Install Wundervault
In a terminal on that computer:
Linux
sudo npm install -g @wundervault/mcp-server@2
With sudo: the helper app won't run a copy in your home folder.
macOS
npm install -g @wundervault/mcp-server@2
Windows
npm install -g @wundervault/mcp-server@2
Already installed? To move to a new version, follow the update steps.
Step 2: Install the helper app
The helper app runs in the background; there’s nothing to open. It gets its own account, with a folder your agents can’t read.
Linux
sudo sh "$(npm root -g)/@wundervault/mcp-server/packaging/install-daemon.sh"
macOS
cd "$(npm root -g)/@wundervault/mcp-server"
sudo sh packaging/install-daemon-macos.sh
Windows
Set-Location (Join-Path (npm root -g) "@wundervault\mcp-server")
powershell -ExecutionPolicy Bypass -File packaging\install-daemon-windows.ps1
To check the installer first, see Install & upgrade.
Step 3: Pair it with your vault
- On the computer, run:
It shows a code and a fingerprint. Paths can differ: use the ones your installer printed. Full paths, because with
Linux
sudo /opt/wundervault/current/node /opt/wundervault/current/app/bin/wundervault-agent --pairmacOS
sudo /opt/wundervault/current/node /opt/wundervault/current/app/bin/wundervault-agent --pairWindows
wundervault-agent --pairsudoa bare name could be found in a folder your agents can write. - In your vault, open Computers and select Pair a computer.
- Enter the code and select Look up.
- Check that the fingerprint matches the one on the computer. Name the computer, then select It matches: pair this computer.
Get help
If the computer says npm isn't found
Install Node.js 22.23.4, 24.22.1 or 26.12.1 or newer from nodejs.org, then open a new terminal.
If it says Node.js lacks the October 21, 2026 security fix
Install Node.js 22.23.4, 24.22.1 or 26.12.1 or newer, then run the step again.
If npm stops with a permission error (EACCES)
On Linux or macOS, run it again with sudo, naming node and npm in full so it works however sudo is set up:
sudo "$(command -v node)" "$(command -v npm)" install -g @wundervault/mcp-server@2
If the installer warns that sudo on this computer looks commands up in a folder someone other than root can change
When you type sudo, your computer looks for the command in a list of folders. One of them can be
changed by your account, so an agent could put a program there and it would run as root the next time you use
sudo for anything. The installer itself is not affected. One line in sudo's settings fixes it for good.
The installer prints four commands with the right folders for your computer: copy them from there and run them one at a time. They write the line to a spare file, check it, and only then put it in place, so a typo can't lock you out of sudo. On a Mac they usually look like this:
sudo /bin/mkdir -p /etc/sudoers.d
printf '%s\n' 'Defaults secure_path="/usr/bin:/bin:/usr/sbin:/sbin"' | sudo /usr/bin/tee /etc/sudoers.d/secure_path.new >/dev/null
sudo /bin/chmod 0440 /etc/sudoers.d/secure_path.new
sudo /usr/sbin/visudo -cf /etc/sudoers.d/secure_path.new && sudo /bin/mv /etc/sudoers.d/secure_path.new /etc/sudoers.d/secure_path
Afterwards, sudo /usr/bin/printenv PATH should list only system folders. Don't use
sudo visudo for this: it opens an editor as root, and which editor it opens can come from the same
settings that are exposed. If the installer says your sudo doesn't read /etc/sudoers.d, the line
belongs in /etc/sudoers itself; ask whoever looks after the computer.
After this, sudo npm may say "command not found": on a Mac, npm and node from nodejs.org are in
/usr/local/bin, which that line leaves out on purpose (Homebrew can make it writable without
sudo). Name both in full instead, as the Mac update steps do:
sudo "$(command -v node)" "$(command -v npm)" install -g @wundervault/mcp-server@2
If the agent says wundervault-agent is not running for agent …
The helper app isn't running on that computer, or the agent hasn't enrolled. Set up the computer, then paste the message again.
More in Troubleshooting.