What problem does it solve? Exposing a local OpenClaw agent to external MCP clients like Grok requires OAuth (PKCE) rather than simple bearer tokens, plus careful nginx, systemd, and TLS configuration—mistakes here expose the Gateway or silently break handoffs. ## Core Features & Use Cases - OAuth MCP ingress: Implement a Streamable HTTP MCP server with PKCE authorization, dynamic client registration, and well-known discovery endpoints using the MCP Python SDK 2.x. - Structured handoff packs: Compact session transcripts into briefs with a mandatory EXECUTE block, persist them to disk, and submit them to OpenClaw via background openclaw agent calls. - Production deployment guidance: Covers nginx TLS binding on eth0 only (avoiding Tailscale IPv6 conflicts), systemd hardening, separate connector secrets, and verification checklists. - Use Case: Connect Grok to a local OpenClaw instance by deploying a loopback connector at https://openclaw-ego.engineer/mcp, registering it in the Grok UI with OAuth fields, and handing off compacted work sessions. ## Quick Start Use this skill to build an OAuth-secured MCP connector that accepts handoffs from Grok and submits them to my local OpenClaw agent.