What problem does it solve? Google's hosted Gmail MCP endpoint does not advertise OAuth metadata, so Hermes's mcp login fails before any browser opens. This Skill provides two working routes to give Hermes full email access: a local gmail-mcp proxy that exposes proper OAuth metadata, and a Himalaya CLI fallback that bypasses OAuth entirely with an app password. ## Core Features & Use Cases - Local Gmail MCP Proxy Setup: Install and run domdomegg's gmail-mcp v2.4.0 with your own Google OAuth client, including the required redirect_port/redirect_host pin so the token exchange succeeds. - Google Cloud Console Guidance: Step-by-step OAuth consent screen, client creation, and test-user configuration, with documented workarounds for computer_use's inability to click Google Console widgets. - Himalaya CLI Fallback: A known-good v2.1.0 config using IMAP/SMTP with a 16-character Gmail app password when OAuth is blocked. - Use Case: You want your Hermes agent to read, search, and send Gmail. Follow Route A to stand up the local proxy, register the redirect URI in Google Cloud, run hermes mcp login gmail, and the token is saved for persistent email tool access. ## Quick Start Set up Gmail access for my Hermes agent using the local gmail-mcp proxy route, and fall back to Himalaya with an app password if OAuth consent is blocked.