What authentication method does ssh-utils use?
Only key-based SSH authentication is supported; password-based authentication is explicitly prohibited for security.
@GrahamJenkins
Basic information
MCP Server featuring multiple SSH related utilities
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
ssh-utils is a Model Context Protocol (MCP) server for executing terminal commands on a remote server via SSH. It is designed for use with Roo Code or any MCP-compatible client, using key-based authentication.
Place the configuration file (ssh-utils-servers.json) in the current working directory, workspace root, or the global config directory (~/.config/ssh-utils/). Then invoke the execute_ssh_command tool from an MCP client, specifying the command and optionally overriding connection parameters.
Only key-based SSH authentication is supported; password-based authentication is explicitly prohibited for security.
The file `ssh-utils-servers.json` can go in the current working directory, the workspace root, or the global config directory `~/.config/ssh-utils/`.
Yes, the configuration file supports multiple profiles. The first profile is used by default, or you can specify a profile by name when invoking the tool.
Any tool arguments such as user, host, or server will override the corresponding values from the configuration file for that command.
The `privateKeyPath` field is optional. If omitted, the SSH client will use the default key discovery mechanism (e.g., keys loaded in the SSH agent).
Mobbin MCP connects your AI agents to 600,000+ real product screens, so what they build starts with what already works.

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

Read and edit DB Planner database schemas (DBML/SQL), Mermaid diagrams and board layouts from any MCP client. 38 tools, OAuth sign-in, read and write as separate scopes enforced server-side.

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.
Comments