SSH-PowerShell MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node.js environment | production |
| LOG_LEVEL | No | Logging level | info |
| SSH_KEY_PATH | No | Path to your SSH private key | |
| COMMAND_TIMEOUT | No | Command timeout in milliseconds | 30000 |
| SSH_DEFAULT_HOST | No | Your default server IP address | |
| SSH_DEFAULT_PORT | No | SSH port number | 22 |
| SSH_DEFAULT_USER | No | Your default SSH username | |
| SSH_STRICT_HOST_KEY_CHECKING | No | SSH strict host key checking setting | no |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ssh_executeC | Ejecutar comandos en máquinas remotas vía SSH usando clave SSH |
| powershell_executeC | Ejecutar comandos PowerShell localmente |
| ssh_scanC | Escanear red para encontrar hosts SSH disponibles |
| ssh_keyscanC | Obtener fingerprint de claves SSH de un host |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: powershell_execute is for local PowerShell commands, ssh_execute is for remote SSH command execution, ssh_keyscan retrieves SSH key fingerprints, and ssh_scan discovers SSH hosts on a network. There is no overlap or ambiguity between these functions.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure: powershell_execute, ssh_execute, ssh_keyscan, ssh_scan. The naming is uniform and predictable across all tools.
With 4 tools, the count is reasonable for an SSH/PowerShell server, covering core remote execution and SSH management tasks. It might be slightly thin for advanced scenarios (e.g., missing file transfer or session management), but it's well-scoped for basic operations.
The toolset covers key SSH and PowerShell operations: remote command execution, host discovery, and key verification. Minor gaps exist, such as no file transfer (e.g., SCP/SFTP) or SSH configuration management, but agents can work around these with the provided tools for most workflows.