What problem does it solve? Adding MCP servers to Hermes Agent fails when users edit config.yaml directly (blocked by a security guard) or when SaaS-hosted remote MCP servers reject OAuth client registration with allowlist-gated 403 errors, leaving users without a clear path to a working integration. ## Core Features & Use Cases - CLI-driven server setup: Add stdio (npx/uvx) or remote HTTP MCP servers using hermes mcp add, with guidance for handling interactive OAuth prompts in non-interactive terminals. - OAuth troubleshooting ladder: Diagnose Registration failed: 403 errors from providers like Figma that allowlist dynamic client registration, with ordered workarounds including client_name overrides, pre-registered client_id, and local desktop MCP variants. - Verification workflow: Confirm servers work using hermes mcp list, hermes mcp test, and /reload-mcp after configuration changes. - Use Case: You try to connect Figma's remote MCP server and hit a 403 during OAuth registration. This Skill walks you through confirming the failure is provider-side, then sets up Figma Desktop's local MCP server at http://127.0.0.1:3845/mcp as the working alternative. ## Quick Start Ask the agent to add a new MCP server to Hermes and verify it connects, or to diagnose why an OAuth-based MCP server login is failing.