What problem does it solve? Hermes MCP servers can appear stuck in a disabled state, the hermes mcp enable subcommand may not exist in your build, and reading the base config.yaml instead of the active profile's file leads to misleading results. This Skill provides the verified command paths and pitfalls for reliably managing MCP server enablement. ## Core Features & Use Cases - Enable/Disable via CLI: Uses hermes config set "mcp_servers.<name>.enabled" against the active profile config located with hermes config path, since config.yaml is blocklisted from direct file edits. - Troubleshooting Reverts: Diagnoses servers that re-disable themselves due to the validate_mcp_server_entry security validator, and handles the hermes mcp list crash caused by string-typed server entries. - OAuth Remote Servers: Walks through manual Google Cloud OAuth client registration for hosted MCP servers (Gmail, Drive, Calendar) that lack Dynamic Client Registration. - Use Case: You run hermes mcp enable time and get invalid choice: 'enable'. This Skill shows you to locate the real profile config, flip the enabled flag with hermes config set, and verify with hermes mcp list. ## Quick Start Ask the agent to enable the disabled MCP server named 'time' in the active Hermes profile and verify it shows as enabled.