What problem does it solve? When ZeusAgent runs as a remote gateway (container, VPS, messaging bot), its built-in MCP OAuth flow fails because the browser redirect to 127.0.0.1 resolves to the user's laptop instead of the remote host, so the authorization code never reaches the agent. This Skill performs the OAuth dance manually and writes tokens into ZeusAgent's expected token storage files. ## Core Features & Use Cases - Manual OAuth 2.1 + PKCE flow: Discovers OAuth metadata via RFC 9728, registers a dynamic client via RFC 7591, builds the authorize URL, and exchanges the pasted callback code for tokens. - Token storage in ZeusAgent's schema: Writes <server>.json and <server>.client.json under $ZEUS_HOME/mcp-tokens/ with correct permissions so /reload-mcp skips the browser flow. - Diagnostic script: scripts/diagnose-oauth-mcp.py smoke-tests stored tokens, attempts refresh, and reports which recovery branch applies (TOKEN_OK, REFRESH_FIXED, SESSION_REVOKED, REFRESH_DEAD). - Use Case: A user runs ZeusAgent as a Telegram bot on Railway and wants to add Linear's OAuth-gated MCP server; this Skill walks through the manual flow and persists tokens without any interactive TTY. ## Quick Start Ask the agent to set up OAuth for a remote MCP server on the headless gateway and paste back the callback URL after authorizing in your browser.