AppDeploy vs Ssh MCP
A side-by-side look at the AppDeploy and Ssh MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AppDeployCoding AgentsAppDeploy turns app ideas described in AI chat into live full-stack web applications37FairAuth: not declaredVerdict: choose AppDeploy for coding agents work; 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 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 | A AppDeploy | |
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 37/100 · Fair | 68/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | SSH_MCP_PASSWORDSSH_AUTH_SOCK |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 819 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 14 |
| Full listing | View AppDeploy | View Ssh MCP |
Tools & capabilities
AppDeploy tools
No tool names declared yet. Check the project README from the listing page.
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.
AppDeploy
No confirmed install command for AppDeploy yet — follow the setup steps linked from its listing page rather than a guessed package name.
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
AppDeploy is categorized under Coding Agents and uses an install path we have not confirmed yet. Ssh MCP belongs to Coding Agents and uses a local stdio subprocess. Pick AppDeploy 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. AppDeploy has no confirmed install command yet — follow its own setup instructions.
AppDeploy 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 appdeploy and tufantunc-ssh-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AppDeploy has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Ssh MCP has 68/100 (Great) with 3 views, 0 installs and 819 GitHub stars.