What problem does it solve? The official remote Gmail MCP endpoint lacks the OAuth discovery metadata Hermes's MCP client requires, so remote login fails with errors like "no OAuth token obtained" or invalid_state. This Skill sets up a local gmail-mcp server on 127.0.0.1:8080 that brokers the Google OAuth consent flow back to Hermes. ## Core Features & Use Cases - Local OAuth Proxy Setup: Installs and configures domdomegg/gmail-mcp with Google OAuth client credentials, correct redirect URIs, and Hermes profile config via hermes config set. - invalid_state Patch: Applies a mandatory patch replacing in-URL state with a file-backed server-side session store, including empty-session guards and exact-match callback validation. - Self-Contained Orchestrator: Runs scripts/oauth_orchestrate.py to register the session, open Chrome on the real Google consent URL, receive the callback code, and write the Hermes token file. - Use Case: When hermes mcp login gmail hangs or fails with State parameter mismatch, use this Skill to complete the Gmail OAuth flow and verify the token at mcp-tokens/gmail.json. ## Quick Start Set up Gmail access for my Hermes agent using the local gmail-mcp OAuth proxy and walk me through the consent flow.