Wiff vs Ssh MCP
A side-by-side look at the Wiff and Ssh MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Wiff for coding agents work as a local process; choose Ssh MCP for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Wiff when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
WIFF_BACKEND. - You want tools like
workflow_start, workflow_status, workflow_wait.
Choose Ssh MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
SSH_MCP_PASSWORD, SSH_AUTH_SOCK. - You want tools like
list-connections, list-sessions, open-session.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 60/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | WIFF_BACKEND | SSH_MCP_PASSWORDSSH_AUTH_SOCK |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 819 |
| Directory activity | 4 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | 14 |
| Full listing | View Wiff | View Ssh MCP |
Tools & capabilities
Wiff tools 5
workflow_startLaunch a deterministic JavaScript workflow in the background, or resume a previous run without repeating successful unchanged agent calls. User and project preferences are loaded from Wiff config. Always pass the caller's absolute working directory as cwd.workflow_statusRead the latest persisted status, phase, counters, result, and artifact paths for a workflow run.workflow_waitWait until a workflow changes state or the timeout elapses. Call repeatedly until the run is completed, failed, cancelled, or interrupted.workflow_cancelInterrupt all live agents and mark a workflow run cancelled.workflow_modelsList the models each agent backend (codex, claude, cursor, kimi) can run, with supported reasoning efforts. Backends that are unavailable on this machine report an error instead of models.
Ssh MCP tools 14
list-connectionsDiscover available hosts and connection statuslist-sessionsList active sessions per hostopen-sessionCreate a named interactive (stateful) or background sessionclose-sessionClose a session. A background session's command is signalled (INT/TERM/KILL) before its channel is droppedread-session-outputRead output from background sessions (e.g., `tail -f`)read-commandExecute allowlisted read-only commands (`ls`, `cat`, `grep`, ...)run-commandExecute arbitrary commands (destructive/privileged need approval, unless `approvalPolicy = "auto"`)privileged-commandExecute with sudo (needs approval, unless `approvalPolicy = "auto"`)sftp-uploadUpload a file via SFTP (replaces the destination unconditionally)sftp-downloadDownload a file via SFTPsftp-listList a remote directory, bounded in entries and bytessftp-upload-fileStream a local file to the remote host, never through model context- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Wiff
{
"mcpServers": {
"wiff": {
"command": "npx",
"args": [
"-y",
"@xxxoooxoxo/wiff"
],
"env": {
"WIFF_BACKEND": "YOUR_WIFF_BACKEND_HERE"
}
}
}
}
Ssh MCP
{
"mcpServers": {
"tufantunc-ssh-mcp": {
"command": "npx",
"args": [
"-y",
"ssh-mcp"
],
"env": {
"SSH_MCP_PASSWORD": "YOUR_SSH_MCP_PASSWORD_HERE",
"SSH_AUTH_SOCK": "YOUR_SSH_AUTH_SOCK_HERE"
}
}
}
}
Frequently asked questions
Wiff is categorized under Coding Agents and uses a local stdio subprocess. Ssh MCP belongs to Coding Agents and uses a local stdio subprocess. Pick Wiff for coding agents work and Ssh MCP for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Wiff has no declared pricing — check the project's own site. Ssh MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add wiff and tufantunc-ssh-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Wiff has a quality signal of 60/100 (Good) with 4 views, 0 installs and 5 GitHub stars. Ssh MCP has 69/100 (Great) with 5 views, 0 installs and 819 GitHub stars.