Troubleshooting
The most common problems when installing and connecting.
command not found: sddvault
Your terminal started before the installer updated PATH. Open a new terminal window, or reload your shell:
PowerShell reads PATH when it starts. Close every PowerShell window and open a new one.
It’s not on my PATH
Add the install folder to PATH yourself, then open a new terminal.
I’m behind a corporate proxy
Set your proxy before running the installer. sddvault uses the same variables afterwards. Use NO_PROXY for hosts that must be reached directly.
Windows SmartScreen warns about an unsigned app
While SDD Vault is in beta the Windows build is not code-signed, so SmartScreen may say “Windows protected your PC”. Choose More info, then Run anyway. Only do this if the command came from {host}.
The agent does not see SDD Vault
Restart the agent after sddvault init. Check that the setup file exists (.mcp.json, .cursor/mcp.json or .vscode/mcp.json) and that its URL has your organization's slug. With a token, check that SDD_VAULT_TOKEN is set in the environment the agent runs in.
The sign-in expired
Run sddvault login again. sddvault whoami shows who is signed in.
A write is refused with conflict
Someone wrote the document after your last read. Read the current revision, merge your change and write again with that revision as expected_revision.
MCP calls are refused at the limit
Free and Pro have a monthly MCP call limit (plan_mcp_call_limit) that resets on the first day of the next month. See the fair use policy or change the plan.