What problem does it solve? OAuth-backed MCP servers (Gmail, Notion, Google Workspace) often fail to connect in Hermes on Windows: the login flow freezes at "Starting OAuth flow...", Google consent returns invalid_state, or the hosted Gmail endpoint exposes no OAuth metadata. This Skill documents the root causes and proven workarounds for each failure mode. ## Core Features & Use Cases - Windows browser hang bypass: Set the SSH_CLIENT environment variable so Hermes skips webbrowser.open(), prints the auth URL, and waits for a manual paste. - Local gmail-mcp proxy setup: Run domdomegg's gmail-mcp as a local HTTP server that advertises proper OAuth metadata, since the hosted gmailmcp.googleapis.com endpoint does not. - Failure-mode fixes: Resolve invalid_state via incognito consent or a server-side session-store patch, and add test users to bypass Google's Testing-mode verification wall. - Use Case: You run hermes mcp login gmail and it hangs forever. This Skill walks you through verifying the local server is up, launching login with SSH_CLIENT set, completing consent in incognito, and registering the correct callback URI. ## Quick Start Ask the agent to fix my hanging Hermes Gmail MCP OAuth login on Windows using the SSH_CLIENT bypass and the local gmail-mcp server.