Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OVRD_{alias}_KEYNoPath to SSH private key file for the specified alias.
OVRD_{alias}_HOSTNoReal hostname or IP address for the specified alias.
OVRD_{alias}_PASSNoSSH password for the specified alias.
OVRD_{alias}_PORTNoSSH port for the specified alias (default: 22).22
OVRD_{alias}_USERNoSSH username for the specified alias.
OVRD_{alias}_SUDO_PASSNoSudo password for the specified alias.
OVRD_{alias}_ENABLE_PASSNoEnable password for network devices (routers/switches) for the specified alias.

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_commandA

Execute a command on an SSH host using a persistent session.

Starts synchronously and waits for completion. If the command doesn't complete within the timeout, it automatically transitions to async mode and returns a command ID for tracking.

The host parameter can be either a hostname/IP or an SSH config alias. If an SSH config alias is provided, configuration will be read from ~/.ssh/config.

For network devices (routers, switches), use enable_password to automatically enter privileged/enable mode before executing commands.

For Unix/Linux hosts requiring sudo, use sudo_password to automatically handle the sudo password prompt. The command will be automatically prefixed with 'sudo' if not already present.

Advanced Features:

  • Automatic timeout handling with async transition

  • Interactive command support with input capability

  • Command interruption (Ctrl+C) for stuck processes

  • Session persistence across multiple commands

list_sessionsB

List all active SSH sessions.

close_sessionB

Close a specific SSH session.

The host parameter can be either a hostname/IP or an SSH config alias.

close_all_sessionsB

Close all active SSH sessions.

read_fileB

Read a remote file over SSH.

Attempts to read using SFTP first. If permission is denied and use_sudo is True or sudo_password is provided, falls back to using 'sudo cat' via shell command.

write_fileB

Write content to a remote file over SSH.

If use_sudo is True or sudo_password is provided, uses sudo via shell commands (tee). Otherwise, attempts to write using SFTP.

execute_command_asyncA

Execute a command asynchronously without blocking the server.

Returns a command ID that can be used to check status, retrieve output, or interrupt. Useful for long-running commands like 'sleep 60', monitoring tasks, or large operations.

Use with companion tools:

  • get_command_status(command_id) to check progress and retrieve output

  • interrupt_command_by_id(command_id) to send Ctrl+C and stop execution

  • send_input(command_id, text) to provide input to interactive commands

get_command_statusB

Get the status and output of an async command.

interrupt_command_by_idA

Interrupt a running async command by sending Ctrl+C.

list_running_commandsB

List all currently running async commands.

list_command_historyC

List recent command history (completed, failed, interrupted commands).

send_inputB

Send input to a running async command and return any new output.

Useful for interacting with commands that require user input, such as:
- Pagers (less, more): send 'q' to quit, space to page down
- Yes/no prompts: send 'y' or 'n'
- Interactive programs: send appropriate responses

Args:
    command_id: The command ID to send input to
    input_text: Text to send (e.g., 'q', 'y

', etc.)

send_input_by_sessionB

Send input to the active shell for a session.

Useful for clearing stuck interactive states or sending input to the current shell.

Args:
    host: Hostname, IP address, or SSH config alias
    input_text: Text to send (e.g., 'q

' to quit pager, '' for Ctrl+C) username: SSH username (optional) port: SSH port (optional)

read_screenA

Read the terminal screen state for a session.

Returns the current screen content from the terminal emulator, including cursor position. Only works when MCP_SSH_INTERACTIVE_MODE=1 is set.

send_keysA

Send special keys or key sequences to a session.

Supports special key tokens:

  • or : Send newline

  • or : Send escape key

  • : Send tab key

  • : Send Ctrl+C (interrupt)

  • : Send Ctrl+D (EOF)

  • : Send Ctrl+Z (suspend)

  • , , , : Arrow keys

  • : Space character

Regular text is sent as-is. Mix special keys with text: "helloworld"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 15 tools

Disambiguation4/5

The tools mostly target distinct areas: session lifecycle, command execution, async job control, file I/O, and interactive terminal input. There is some overlap among send_input, send_input_by_session, send_keys, and interrupt_command_by_id versus sending Ctrl+C, but descriptions clarify command-scoped versus session-scoped usage.

Naming Consistency5/5

All tool names use snake_case with a verb-first pattern such as list_sessions, close_session, execute_command, read_file, get_command_status, and send_input. Suffixes like _async and _by_id are descriptive and do not break the overall convention.

Tool Count4/5

Fifteen tools is at the high end of a reasonable range but matches the server's broad scope across SSH sessions, async commands, file operations, and interactive terminals. Most tools earn their place, though the interactive input surface adds some density.

Completeness4/5

Core SSH workflows are covered: session lifecycle, synchronous and asynchronous command execution, command monitoring, file read/write, and interactive input. Minor gaps include no explicit session-open tool and no dedicated directory or file-management operations like mkdir, rm, or listing, though these can be handled via execute_command.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues