From da519ebc5cd5b112e88e661c134be570633d177f Mon Sep 17 00:00:00 2001
From: Teknium <127238744+teknium1@users.noreply.github.com>
Date: Mon, 20 Jul 2026 00:05:32 -0700
Subject: [PATCH] fix(dashboard): fold one-field mcp category into agent tab

The new top-level mcp: config section surfaces exactly one field
(auto_reload_on_config_change) in the dashboard settings schema, which
tripped the no-single-field-categories invariant. Merge it into the
agent tab like onboarding/computer_use.
---
 hermes_cli/web_server.py | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/hermes_cli/web_server.py b/hermes_cli/web_server.py
index 1ea775f50366..93bd2447ecd6 100644
--- a/hermes_cli/web_server.py
+++ b/hermes_cli/web_server.py
@@ -779,6 +779,11 @@ _CATEGORY_MERGE: Dict[str, str] = {
     # with the other messaging-platform config (discord) so it isn't an
     # orphan tab of one field.
     "telegram": "discord",
+    # `mcp.auto_reload_on_config_change` is the only schema-surfaced mcp
+    # runtime field (server definitions live under mcp_servers, edited via
+    # the MCP tab) — fold it into the agent tab rather than spawning a
+    # one-field orphan category.
+    "mcp": "agent",
     # `computer_use.cua_telemetry` is the only schema-surfaced computer_use
     # field — fold it into the agent tab rather than spawning a one-field
     # orphan category.