Devolutions ForumDevolutions Forum

RDM MCP — RDM_execute_opened_connection_action not working on SSH sessions

RDM MCP — RDM_execute_opened_connection_action not working on SSH sessions

avatar
danieliwaszkiewicz

Hi,

Is RDM_execute_opened_connection_action expected to be functional in the current experimental MCP version, or is it still work in progress? If it should work — is there a known workaround or additional configuration required?

Version: Remote Desktop Manager 2026.2.8.0
Feature: MCP Server (experimental)

Issue
Calling RDM_execute_opened_connection_action on an active SSH (SSHShell) session always returns a generic error, regardless of the action used.
The connection is visible in RDM_list_opened_connections and all actions (send_command, get_terminal_status, take_screenshot) are listed as available via RDM_list_opened_connection_actions — but none can be executed.
Example call


json
{
"actionName": "send_command",
"connectionIds": ["b22f1d22-22e2-4bfs-b2cf-222e6c1d7151"],
"parameters": {
"command": "date",
"captureOutput": true,
"timeout": 30000
}
}
Error: An error occurred invoking 'RDM_execute_opened_connection_action'.
Same error occurs for get_terminal_status and take_screenshot. RDM was in the foreground with the SSH tab active.

BR
DI

All Comments (1)

avatar
Maxime Forest

Hi @danieliwaszkiewicz,

Let me introduce myself first. I'm Maxime, AI Software Architect, I am the developer of the MCP server and the AI Assistant in RDM.

I'll answer your question about whether it should work first, then go into more detail about my findings. Yes, it should work. I just tested it locally in RDM with the AI Assistant using 3 SSH entries (Linux, macOS, Windows) and on the same 3 entries using an MCP client (VSCode) connected to RDM. I'm experiencing some lag and timeouts on my end, and RDM is slow when I send the prompt to get the top 3 processes on my Windows machine. I'll have to investigate that further with my colleague responsible for the SSH terminal, as there is tight integration with it to extract the output of the command.

We have the same request structure being sent to the MCP server, so the issue is not that

  "actionName": "send_command",
  "connectionIds": [
    "<redacted>"
  ],
  "parameters": {
    "command": "<redacted>",
    "captureOutput": true,
    "timeout": 30000
  }
}


Can you provide more information about your SSH entry so that I can investigate in the right direction? Is it Windows, Linux, or macOS machine? If it's Windows, then what I mentioned about the lag and timeout issues might explain it. If it's Linux or macOS, then I'll need to investigate further.

I'll start investigating the Windows-specific issues while I wait for your reply.

Thanks,

Maxime Forest

Ends in 5 days