MCP server shows as failed in OpenGUI settings even though it works in OpenCode and active sessions

[touch2be]

Description

An MCP server is shown as failed in the OpenGUI MCP settings, even though the same server works correctly in OpenCode and also works inside an active session.

This suggests that there is likely a problem in how OpenGUI detects, initializes, or validates MCP servers in the settings UI.

Observed Behavior

• The MCP server works correctly in OpenCode
• The MCP server also worked in a previous session
• In OpenGUI, the MCP settings page shows the server as failed
• Example error shown in the UI: MCP error -32000: Connection closed
• OpenGUI appears to mis-detect or incorrectly report the MCP server state

Expected Behavior

• If the MCP server is functional and can be used in OpenCode or active sessions, OpenGUI should recognize it correctly in the MCP settings
• The settings page should show the real connection state instead of a false failure
• If there is a configuration mismatch, OpenGUI should surface a clearer explanation of what is wrong

Why This Seems Like a Settings/UI Issue

• The MCP server is not fundamentally broken, because it already works elsewhere
• The problem seems specific to OpenGUI MCP settings handling or status detection
• This creates confusion because the UI reports a failure even though the server is actually usable

Environment

• OpenGUI Desktop Interface
• MCP server works in OpenCode
• MCP server worked in active session
• OS: Linux