What problem does it solve? Hermes's hosted MCP OAuth login for Google services stalls or fails because Google's hosted endpoints do not expose RFC 9728 OAuth metadata, and on Windows the browser auto-open call can block forever, leaving the flow frozen at "Starting OAuth flow...". ## Core Features & Use Cases - Local OAuth-proxy MCP server: Runs the gmail-mcp npm package on localhost so Hermes discovery succeeds and consent redirects work with any redirect URI. - Windows hang workaround: Uses the SSH_CLIENT environment variable to force headless mode so the auth URL prints instead of blocking on webbrowser.open(). - Zombie server detection: Verifies the live server's actual client_id via curl to catch stale processes answering with corrupted credentials. - Use Case: You want Hermes to read and send Gmail through MCP tools, but hermes mcp login gmail freezes; this Skill walks you through standing up the local proxy, configuring the Google Cloud OAuth client, and completing consent. ## Quick Start Ask the agent to connect Gmail to Hermes MCP by starting the local gmail-mcp proxy server and running the login command with SSH_CLIENT set.