connect-to-server-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONNECT_MCP_CONFIG | No | Path to the host inventory YAML. Defaults to ~/.config/connect-to-server-mcp/hosts.yaml | |
| CONNECT_MCP_PYTHON | No | Interpreter to run the server with, bypassing uv/venv discovery. | |
| CONNECT_MCP_SOURCE | No | pip/uv spec to install instead of the published package. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_hostsA | List every configured host with its access mode and description. |
| reload_hostsA | Reload the inventory file from disk and drop all open connections. |
| check_connectionB | Open (or reuse) the SSH connection to a host and report basic identity. |
| run_commandA | Run a shell command on a host, subject to that host's access policy. Read-only hosts accept only inspection commands; anything that appears to modify state is refused before it reaches the server. |
| read_fileB | Read a remote file over SFTP. |
| write_fileA | Overwrite a remote file. Refused on read-only hosts. |
| list_directoryB | List a remote directory with sizes and permissions. |
| tail_logB | Tail a log file or a systemd unit's journal. |
| service_statusB | Show the status of a systemd unit. |
| service_controlB | Start, stop, restart, reload, enable or disable a systemd unit. |
| system_overviewB | Collect a health snapshot: load, memory, disk, top processes, failed units. |
| disconnectB | Close the SSH connection to one host, or to every 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 12 tools
Every tool targets a distinct operation: host inventory, connection lifecycle, general shell commands, file reading/writing/listing/tailing, systemd status/control, and health snapshots. Although run_command is broad, each specialized tool has a clear role and boundary, so misselection is unlikely.
Most tools use an imperative verb-noun pattern like list_hosts and read_file, but service_status, service_control, and system_overview use noun-noun forms, and disconnect is a bare verb. This mixed convention is still readable but not as predictable as a consistent pattern.
With 12 tools, the server is well-scoped for its stated purpose: inventory, connections, shell, file operations, services, and system health all have dedicated coverage. This count is neither too thin nor overly heavy.
The tool set covers core remote-host workflows: list/reload hosts, connect/disconnect, run commands, read/write/list/tail files, manage systemd services, and get a system overview. Missing capabilities like file delete/move/upload or inventory editing are generally workaroundable with run_command or external config management, so the surface is nearly complete.