mcp-oauth-remote-gatewaylisted

# MCP OAuth on a Remote Hermes Gateway ## Overview Hermes' built-in MCP OAuth client runs a one-shot HTTP listener on `127.0.0.1:<port>` inside the Hermes process and registers that loopback address as the OAuth `redirect_uri`. That works perfectly for a local CLI on the user's own machine. It breaks completely when Hermes runs as a remote gateway (container, VPS, messaging bot), because the user's browser resolves `127.0.0.1` to the user's own laptop, not the remote container — so the authorization code never reaches Hermes. This skill does the OAuth dance by hand and writes the resulting tokens into the exact files Hermes' token storage expects, so a subsequent `/reload-mcp` finds cached tokens and skips the browser flow entirely. ## When to Use Use this skill when **all** of the following are true: 1. The user wants to add a remote HTTP MCP server that requires OAuth (not a static Bearer token). 2. Hermes is running as a **remote gateway** (container, VPS, Docker, managed service) — NOT a local CLI on the user's laptop. 3. The server supports OAuth 2.1 with PKCE and RFC 7591 Dynamic Client Registration (most modern MCP servers do — Better Stack, Linear, Cloudflare, Datadog, etc.). If it doesn't support DCR (GitHub is the notable exception), this skill does not apply — use a pre-registered OAuth App or a Personal Access Token instead. Do NOT use this for: - **Local CLI Hermes** — just set `auth: oauth` in `mcp_servers.<name>` and `/reload-mcp`. The built-in flow open