Skip to main content
Glama
nqmn

SSH Remote MCP Server

by nqmn

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ssh_connectA

Connect to a remote Ubuntu server via SSH

ssh_connect_savedB

Connect to a remote server using a saved local SSH credential name

ssh_setup_key_authA

Generate a local SSH keypair, install the public key on the remote server, and save a key-based credential for future connections

ssh_executeB

Execute a command on a remote SSH connection

ssh_upload_fileB

Upload a local file from an allowed local root to the remote server via SFTP

ssh_download_fileA

Download a remote file to an allowed local root via SFTP

ssh_save_credentialsA

Save SSH credentials locally under a reusable name. If a password is provided, the server is contacted once to bootstrap a key and only the generated key credential is saved.

ssh_list_saved_credentialsA

List saved local SSH credential entries

ssh_delete_saved_credentialsA

Delete a saved local SSH credential entry

ssh_disconnectA

Disconnect from a remote SSH connection

ssh_list_connectionsA

List all active SSH connections

ssh_health_checkB

Check the health of SSH connections

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct action on SSH connections or credentials. For example, ssh_connect and ssh_connect_saved differ by credential source, ssh_execute and ssh_download_file/ssh_upload_file are clearly different operations. No overlapping purposes detected.

Naming Consistency4/5

All tools use a consistent 'ssh_' prefix and verb_noun pattern (e.g., ssh_connect, ssh_execute, ssh_download_file). Minor deviation: ssh_setup_key_auth and ssh_delete_saved_credentials use slightly longer verbs but still follow the pattern.

Tool Count4/5

12 tools is reasonable for an SSH management server covering connection lifecycles, file transfer, and credential management. Slightly on the higher end but each tool is justified.

Completeness4/5

Covers core SSH operations: connect/disconnect, execute, file transfer, credential management, and health check. Minor gap: no explicit tool for listing remote files/directories, but file transfer tools imply that capability.

Maintenance

ActivityInactive
ResponsivenessNo issues