MCP Remote Access
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ssh_connectA | Connect to a remote host via SSH. Returns a connection ID for subsequent commands. |
| ssh_executeB | Execute a command on a connected SSH host. Returns stdout, stderr, and exit code. |
| ssh_uploadB | Upload a file to the remote host via SFTP. |
| ssh_downloadB | Download a file from the remote host via SFTP. |
| ssh_disconnectC | Close an SSH connection. |
| ssh_list_connectionsB | List all active SSH connections. |
| ssh_execute_backgroundA | Execute a long-running command in the background. Returns a task ID and output file path. Use ssh_check_background to monitor progress. |
| ssh_check_backgroundA | Check status and get output from a background command. Returns whether it's still running and the latest output. |
| ssh_list_backgroundB | List all background tasks and their status. |
| serial_list_portsB | List available serial ports on the system. |
| serial_connectC | Connect to a serial port. Returns a connection ID. |
| serial_connect_matchB | Connect to a serial port by matching VID/PID/serial/description. Returns a connection ID. |
| serial_sendB | Send data to a serial port. Optionally wait for and return response. |
| serial_readC | Read available data from a serial port. |
| serial_disconnectC | Close a serial port connection. |
| serial_list_connectionsB | List all active serial connections. |
| serial_set_dtrB | Set DTR (Data Terminal Ready) line state. Used for device reset on many boards. |
| serial_set_rtsB | Set RTS (Request To Send) line state. Used for bootloader entry on ESP32/STM32. |
| serial_reset_deviceA | Reset an embedded device using DTR/RTS sequence. Supports ESP32, STM32, and generic reset. |
| serial_flushA | Flush serial buffers (clear pending input/output data). |
| serial_wait_forB | Wait for a specific string/pattern in serial output. Useful for boot messages, prompts. |
| serial_expectC | Wait for patterns and optionally send responses. Useful for login prompts and AT flows. |
| serial_send_breakA | Send a serial break signal. Used to interrupt U-Boot, enter debug modes. |
| serial_esp32_connectA | Connect to ESP32 with automatic reset and boot wait. Handles the ESP32 boot sequence (74880 baud boot messages, then app at 115200). Resets the device and waits for it to be ready. |
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 24 tools
The SSH and serial tool groups are clearly separated by prefix, and within each group the actions are distinct (connect, execute, disconnect, list, etc.). The only minor ambiguity is between serial_expect and serial_wait_for, which both wait for patterns, though expect adds optional response sending.
Most tools follow a consistent transport_verb pattern (ssh_connect, serial_send, serial_disconnect). Minor deviations include serial_connect_match and serial_esp32_connect, which are more specific but still readable and consistent with the overall convention.
24 tools is on the higher end but justified by covering two distinct transports (SSH and serial) with connection lifecycle, data operations, and device-specific helpers. A few tools like serial_flush and serial_read could potentially be merged, but the count is not excessive for the scope.
The tool set covers the full lifecycle for both SSH (connect, execute, background, upload/download, disconnect) and serial (connect, send, read, expect, reset, disconnect). Minor gaps include no SSH port forwarding or serial line settings (baud/parity) configuration, but core remote access workflows are well covered.