Credentials never leave iLead
Standalone SSH MCP packages often keep host passwords or key paths in yet another config file. iLead reuses the Argon2id vault you already trust. Agents see host metadata only.
Model Context Protocol
Local SSH MCP for Cursor, Claude Code, and Copilot
Give AI coding agents controlled access to the SSH hosts already in your encrypted iLead vault — without pasting keys into chat, without a hosted bastion, and without a cloud copy of your fleet. Every command stops for your approval in the desktop app.
Why this MCP is different
Vault-backed SSH for agents, not a second credential store
Approve once, every time
run_command opens a native dialog with the exact host and shell command. Deny is the default. Approved runs are written to the command audit log with source mcp.
Loopback only
The HTTP MCP endpoint binds to 127.0.0.1, requires a Bearer access key, rejects non-local origins, and shuts down when the vault locks. There is no relay server.
Multi-hop still works
Jump / bastion chains configured on a host are used internally for MCP commands. Agents never see or manage the intermediate hops.
Setup
Three steps to wire Cursor or Claude to your vault
- Unlock iLead → Settings → Agent Access (MCP) → Enable MCP. Check only the hosts an agent may touch.
- Copy the ready-made config for Cursor (
.cursor/mcp.json), Claude Code, VS Code, GitHub Copilot, or freebuff. Paste the one-time access key as the Authorization Bearer value (VS Code prompts for it). - Restart the client. Ask it to call
list_hosts, thenrun_command. Approve or deny each run in iLead.
Tools exposed today
list_hosts— allowed saved hosts (id, name, address, port, user; never secrets)run_command— shell command on one allowed host after desktop approval (output may be truncated)
That surface is intentionally small and reviewable. It is mature enough for day-to-day agent workflows that need inventory + one-shot diagnostics, without turning your vault into an unsupervised remote shell API.
SEO answers
SSH MCP FAQ
Is iLead an SSH MCP server?
Yes. iLead embeds a local Model Context Protocol bridge so MCP clients on the same machine can use selected vault hosts. It is not a hosted MCP gateway and not a replacement for your SSH client UI.
How is this different from generic ssh-mcp npm packages?
Generic packages are useful, but they usually manage their own SSH config and often skip a human approval gate tied to a desktop vault. iLead's differentiator is the encrypted inventory, allowlist, per-command dialog, audit trail, and multi-hop support you already configured for yourself.
Does MCP work with the Mac App Store or Microsoft Store build?
Yes — MCP ships in the desktop app, including the Mac App Store build. Keep iLead unlocked while the agent runs; locking the vault stops the bridge. Use the in-app client configs rather than inventing a public URL.
Prefer a full product comparison? See iLead vs PuTTY, MobaXterm, Termius, and SecureCRT or the feature list.