danieliwaszkiewicz

Hi Maxime,

After a restart it started working! Successfully retrieved CPU, RAM, and disk info from a Linux SSH session via MCP. Great work on the fix!

Thanks,

Daniel

I have the same version: 1.22209.3 (babe11) from 2026-07-19

Claude 1.22209.3 (babe11) 2026-07-19T02:06:35.000Z

Daniel

Hi Maxime,

I've checked and I already have the latest version of Claude Desktop installed, but the issue still persists — RDM_execute_opened_connection_action keeps returning the same generic error for all actions on both SSH and RDP connections.

Could you confirm which exact version of Claude Desktop you were testing with?

Thanks,

Daniel

Hi Maxime,

A few things to report after testing version 2026.2.14 (Jetsocat [Devolutions.Jetsocat] Version 2026.2.3):

1. RDM_execute_opened_connection_action still not working

The fix mentioned in the release notes doesn't seem to have taken effect on my end — RDM_execute_opened_connection_action still fails for all actions (send_command, get_terminal_status, get_connection_info, take_screenshot, close_connection, logoff) on both SSHShell and RDPConfigured connections. The error returned is always the same generic message with no details.

2. Clicking "Background Services" crashes RDM

Steps to reproduce:

Open RDM

Open Claude Desktop — MCP connection is established successfully

Click Background Services in the RDM menu

RDM crashes and closes completely

After the crash:

Reopening RDM does not restore the MCP connection — a full Claude Desktop restart is required

MCP server settings are not saved — options like "Start server on startup", "Automatically approve new MCP client connections" and "Exclude sensitive data (passwords) from responses" are reset to defaults after every crash

The log at the time of crash shows $/proxy/serverDisconnected — RDM itself sends the disconnect signal before closing.

Are these known issues in 2026.2.14, or would it be worth doing a clean reinstall and testing again from scratch?

Thanks,

Daniel

Hi Maxime,

Any update on the fix? Is it already included in one of the recent releases?

Thanks,

Daniel

After more testing, I can confirm the issue is not specific to SSH or to send_command. All actions via RDM_execute_opened_connection_action fail regardless of connection type.

Tested and failing: send_command, get_terminal_status, get_connection_info, take_screenshot on SSHShell, and send_command, take_screenshot, close_connection, logoff on RDPConfigured.

In every case the error returned is the same generic message: "An error occurred invoking 'RDM_execute_opened_connection_action'." — no details, no stack trace, no error code.

All other MCP tools work fine (RDM_search_entries, RDM_copy_entries, RDM_create_folders, etc.), so it seems the issue is isolated entirely to RDM_execute_opened_connection_action.

Should I test this with a different AI? Could it be a claude desktop issue?

Hi Maxime,

The use case was copying ~80 entries (26 per folder × 3 sub folders) into a new folder structure, sent in parallel batches of 4–10 entries per RDM_copy_entries call.

Honestly, I think the main bottleneck might just be Hub Business itself — even when I move or copy a larger number of entries manually in RDM, it also takes quite a while. So the MCP timeouts might simply reflect that underlying latency rather than anything specific to the MCP layer.

Thanks,

Daniel

Hi Maxime,

Thanks for the quick response and for testing this yourself!

Here are the details:

• RDM client OS: Windows (Cloud Desktop)

• SSH target: Linux (Ubuntu), standard username/password authentication

• Connection type: Regular SSH session (no key-based auth, no jump host)

• Session state: The SSH connection was open and active in RDM at the time of the MCP call — I could see the terminal tab with the session running

• Datasource: Devolutions Hub Business (not a local database)

The error was consistent across all three actions (send_command, get_terminal_status, take_screenshot), so it doesn't seem action-specific.

On a positive note — other MCP operations like creating folders, moving/copying entries, and importing work very well overall. I do experience some lags and timeouts there too, but the operations complete successfully on the Hub side even when the MCP call times out on the client.

Let me know if you need any additional details or logs.

Thanks,

Daniel

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

Hi

Any information on this matter because I have the same error ?

Best regards