Configuration does not work when installed globally

[jantman]

Following the README after a npm install -g mcp-ssh-manager, and then having symlinked /usr/local/bin/ssh-manager to /usr/lib/node_modules/mcp-ssh-manager/cli/ssh-manager as a workaround for #18 , adding a server fails:

$ ssh-manager server add
...
Configuration Summary
----------------------------------------
Name:                something
Host:                something.example.com
User:                jantman
Port:                22
Auth:                key
Key:                 /home/me/.ssh/id_rsa

Save this configuration? [Y/n]: Y
cp: cannot stat '/usr/lib/node_modules/mcp-ssh-manager/.env': No such file or directory
$

[bvisible]

Thanks for the detailed report! Fixed in v3.2.2 (together with #18).

The root cause was that the CLI resolved the .env path relative to the script location, which points inside node_modules for global installs. The fix implements a fallback chain (consistent across both the CLI and the MCP server):

1. ~/.ssh-manager/.env (user config directory — new default for global installs)
2. $PWD/.env (current working directory)
3. ~/.env (home directory)
4. <project-root>/.env (backward compat for local/dev installs)

Additionally, ssh-manager server add now creates ~/.ssh-manager/.env and its parent directory automatically if they don't exist yet.

Please upgrade with npm install -g mcp-ssh-manager and let me know if it works for you.

[jantman]

@bvisible Thanks so much for the attention on this. I ended up just looking at the code and setting up the config myself.