MCP server¶
Voltius can act as an MCP server, so an AI agent running on your computer — Claude Code, Claude Desktop, Cursor, Cline, Windsurf, VS Code with Copilot, OpenCode — can use your saved hosts directly. The agent opens sessions, runs commands, reads and writes files over SFTP, creates or deletes connections, keys and identities, and reorganises your vaults and folders, using the credentials already in your vault. You never paste a private key into a chat window.
It is off by default and lives entirely on your machine.
Read the security model before you enable this
Turning this on grants any process running as you that can open the socket full command and file access to every host in your vault and to this computer. Voltius does not prompt per call — see What you are granting.
Enabling it¶
Settings → Integrations → MCP. Flip the toggle; the row shows Running once the socket is up. Turning it off closes the socket and disconnects any attached client.
Enabling the server is not enough on its own — your client also has to be told Voltius exists.
Connecting a client¶
Quick setup¶
Quick setup shows a one-line command to copy and run in your terminal. It uses add-mcp, which detects the AI agents installed on this computer and registers Voltius with all of them, leaving your other MCP servers untouched. It needs Node.js. The command is:
The -y there is npx's, and only skips the "install this package?" prompt. add-mcp itself still asks for confirmation and shows which agents it will configure before writing anything. That prompt is deliberate: these are config files on a machine where Voltius holds your SSH credentials.
Manual setup¶
No Node.js, or a client add-mcp doesn't know about? Manual setup in the same panel reveals a copyable snippet per client, already filled in with this installation's executable path.
Add to claude_desktop_config.json or .cursor/mcp.json:
Add to .vscode/mcp.json:
VS Code uses servers, not mcpServers — pasting a Cursor-style block here silently loads nothing.
Every client speaks stdio to voltius mcp, a thin shim that forwards to the running app. Voltius has to be open — the shim is not a headless server, and a client that starts while the app is closed gets no tools.
What the agent can do¶
94 tools, grouped by what they touch. Names are exactly what the agent sees.
| Group | Tools |
|---|---|
| Connections | list_connections · connection_get · connection_create · connection_update · connection_delete · connection_bulk_import · ssh_config_sync |
| Keychain | key_list · key_create · key_delete · key_add_to_host · identity_list · identity_create · identity_delete · known_host_list · known_host_trust · known_host_delete |
| Sessions | list_sessions · open_session · run_command · send_keys · read_terminal · close_session · history_search |
| Panes | pane_list · pane_split · session_move_to_pane · pane_detach · pane_focus · pane_rename · tab_rename |
| Files | list_files · stat_file · read_file · write_file · make_dir · rename_path · delete_path · transfer_file · transfer_list · transfer_cancel · transfer_retry |
| Snippets | snippet_list · snippet_create · snippet_update · snippet_delete · snippet_run |
| Port forwarding | port_forward_list · port_forward_create · port_forward_update · port_forward_delete · port_forward_tunnels · port_forward_start · port_forward_stop |
| Vaults | vault_list · vault_create · vault_rename · vault_delete |
| Folders | folder_list · folder_create · folder_rename · folder_delete |
| Objects | object_move · object_copy · export_objects · import_objects |
| Team | team_list · member_list · vault_key_status · member_invite · member_remove · member_set_role |
| Sharing | list_shared_sessions · share_session · unshare_session · handoff_control |
| Settings | setting_list · setting_get · setting_set |
| Plugins | plugin_list · plugin_install · plugin_uninstall · plugin_enable · plugin_disable · plugin_update · plugin_configure · marketplace_search · marketplace_source_list · marketplace_source_add · marketplace_source_remove |
| Status | sync_status · host_ping_status · subscription_status · audit_query |
sync_status reports Voltius Cloud and each sync provider plugin. It does not cover local network sync.
open_session opens a saved connection. run_command, send_keys and read_terminal also work on any session already open in the app, including your own local shells and serial devices. transfer_file copies files between any two ends the app can reach, including host to host.
key_add_to_host appends a saved key's public half to a host's authorized_keys over SSH, using that connection's stored credentials — it writes to the remote machine. It takes a key id and a connection id, never a script: the destination is confined to a relative directory under the remote home (location, default .ssh) and a plain filename (filename, default authorized_keys), an unsafe location or filename is refused, every value is shell-quoted before it is sent, line breaks are stripped from the key's name, and a public key that is not one valid line is refused rather than sent.
vault_delete refuses a vault that still holds anything unless cascade is true, and always refuses the personal vault. Folders live in four separate trees — hosts, keychain, port forwarding and snippets — so folder_create takes a kind and folder_list filters on it. Folder deletion cascades.
object_move and object_copy are the cut/copy-and-paste the pages already do, exposed as verbs. They take the ids of objects of one kind (connections, keys, identities, snippets or port forwarding rules), optionally folder ids so whole subtrees travel too, and a destination folder and/or vault. Landing objects in a vault other than their own is refused unless allow_cross_vault is true, and the refusal names how many objects would move and where — an agent that guessed a destination is told, not obeyed.
A team-vault object refuses changes the same way the UI does: an agent calling connection_update on a connection owned by a team vault gets an error, and nothing is written. The newer verbs hold the same line — renaming or deleting a team vault or one of its folders, and copying an object out of a team vault, are all refused.
ssh_config_sync rereads ~/.ssh/config and brings the hosts it manages up to date, on desktop only. It returns how many hosts were created, updated and removed, and which aliases are not synced and why. It is refused while continuous sync is off: an agent cannot turn it on. It also fails, without changing anything, while Voltius sync is paused, before this computer has been reviewed, or when ~/.ssh/config keeps changing during the read. On a host managed by that sync, connection_update refuses the fields the file controls, and still accepts the rest, such as the name.
Tools your plugins add¶
Installed plugins can contribute their own tools, so the agent grows with the app. Four of the bundled plugins add 15:
| Plugin | Tools |
|---|---|
| Docker | docker__container_list · docker__container_action · docker__container_logs · docker__image_list · docker__volume_list · docker__network_list · docker__stack_list |
| Proxmox | proxmox__lxc_list · proxmox__lxc_action · proxmox__snapshot_list · proxmox__snapshot_create · proxmox__snapshot_rollback |
| Process manager | process-manager__process_list · process-manager__process_kill |
| System monitoring | monitoring__metrics_snapshot |
Settings → Integrations → Plugin tools exposed to clients lists every plugin that contributes tools, with a per-plugin toggle. Turning one off removes its tools from the list and refuses calls to them — an agent that already had the list is told immediately that the tool list changed. Third-party plugins must hold the danger-gated mcp:contribute permission, which you grant explicitly at install.
What you are granting¶
This is the part worth reading twice.
- Approval happens in the client, not in Voltius. Claude Code and friends have their own approval UI; that is the layer that asks before a command runs. Voltius performs no per-call check by construction — it is a tool provider, not a second gate.
- The reach is your whole vault, plus this computer. Every saved host, key and identity, the folder and vault structure they live in, every terminal already open in the app (your local shells included), every app setting, your plugins and marketplace sources, and, if you are in a team, its membership and your shared sessions. Deletion verbs are included and are not undoable —
vault_deletewithcascadeandfolder_deletetake their contents with them, andkey_add_to_hostwrites to a remote machine. - Anything running as you that can open the socket has that reach. The socket is protected by the operating system's own access control, not by a token Voltius issues.
Access is scoped by the OS:
- Linux and macOS — a Unix socket at
<config>/voltius/mcp/mcp.sock, mode0600, inside a0700directory. - Windows — a named pipe at
\\.\pipe\voltius-mcp-<username>, with a DACL granting only your own user SID (and the SYSTEM account), created withFILE_FLAG_FIRST_PIPE_INSTANCEso a squatted pipe name fails loudly instead of quietly handing your agent to another process.
The connection between your agent and Voltius never crosses the network. Tools that act on your team, shared sessions or sync talk to the Voltius server the same way the app does.
The audit trail¶
Voltius writes an audit row for calls that change something — the host writes it, not the plugin, so a plugin cannot forget to. Rows record which tool ran, which plugin contributed it, and which connection it touched. For plugin tools, argument values are never recorded. For the built-in tools, the command text of run_command and the arguments of file operations (paths, and what write_file wrote) are kept in the row on this device only; they never reach the server. Team-vault activity also lands in that vault's audit log. An agent can read its own trail with audit_query.
Troubleshooting¶
The client lists no tools. The server must be running (Settings → Integrations shows Running) and the app must be open. Restart the client after enabling — most clients read the tool list once at startup.
VS Code loads nothing at all. Check you used servers and not mcpServers.
A plugin's tools are missing. Check the per-plugin toggle in Plugin tools exposed to clients, and that the plugin is enabled in Settings → Plugins.
A session call is refused with "session not opened by this MCP server". close_session, the pane verbs and share_session/unshare_session act only on sessions an MCP client opened. A session you opened yourself can't be closed, split or shared by the agent, and neither can one that another connected client still holds. Sessions left behind by a client that disconnected are adopted by the next client that uses them.