mcp-remote-control
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MRC_HOME | No | Configuration root directory. Defaults to ~/.config/mcp-remote-control. | ~/.config/mcp-remote-control |
| MCP_REMOTE_CONTROL_HOME | No | Alternative environment variable for configuration root. If MRC_HOME is not set, this is used. |
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 |
|---|---|
| endpointA | Host endpoint lifecycle only: op=list|open|close. open uses profile=; close uses ep=. Not for serial ports — use the console tool. |
| execC | Remote non-interactive exec on ep=. Provide command= or argv= or script=/script_path=; optional runtime=, script_args=, cwd=, timeout=. |
| fsC | Filesystem on ep=: op=list|stat|read|write|put|get|mkdir|rm; path= absolute preferred. |
| screenA | Interactive PTY screen on host ep=: op=open|send|close|list. Loop: open → frame → send(actions) → frame → close. Not for serial hardware — use the console tool. |
| psB | Persistent PowerShell runspace (WinRM): op=open|invoke|close. open needs ep=; invoke/close need id=; invoke uses script=. |
| consoleA | Serial Console (embedded device link on this host; not PTY/SSH). op=list|open|send|views|close|sessions. list: system device= names (do not scan /dev or drivers). open: path= or device= from list, optional baud=, max_lines= (default huge buffer; background capture starts immediately). send: id= + data= or data_b64=, optional newline=. views: id= + mode=tail|since|contains; n=; since=; contains=; context=; settle_ms=; with_seq=; queries capture buffer (not driver recv). close/sessions: id= / list open sessions. |
| configA | Complete self-config for profiles. Do NOT shell-edit config files. ops: help|home|ensure_home|get|list_profiles|get_profile|put_profile|delete_profile|put_secret|list_secrets. Password is NOT private — write it inline: put_profile name=lab transport=ssh host=… username=… auth={"method":"password","password":""} ssh={"known_hosts":"none"} then endpoint open profile=lab. SSH key still uses put_secret + key_path=secrets/…. WinRM: auth password=plain + winrm={scheme,auth}; optional defaults/caps. op=help for recipes. |
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 7 tools
Each tool targets a distinct resource or action: endpoint manages host lifecycle, exec runs non-interactive commands, fs handles filesystem operations, screen provides interactive PTY, ps manages PowerShell runspaces, console handles serial devices, and config manages profiles. Overlapping tools like screen and console are explicitly differentiated by hardware type, while exec and ps differ in interactivity and persistence.
All tool names are single lowercase words (endpoint, exec, fs, screen, ps, console, config) following a consistent, predictable pattern. There is no mixing of conventions such as camelCase or snake_case.
Seven tools is well-scoped for a remote control server, covering all major operation areas (connection, command execution, files, terminal, PowerShell, serial, configuration) without unnecessary overlap or bloat.
The tool set provides comprehensive coverage of remote management workflows: endpoint lifecycle, command/script execution, file transfer and manipulation, interactive sessions, persistent PowerShell, serial console access, and profile/secret configuration. There are no obvious dead ends or missing critical operations.