Individual skill
mcp-oauth-remote-gateway
Manual OAuth for remote MCP servers on headless gateways.
optional-skills/mcp/mcp-oauth-remote-gateway/SKILL.md
Source commit e8639fd4312e5102d6f10c76b56406cb01c19092
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 261,005
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 23,987 bytesSKILL.mdcore · 23,987 bytesSKILL.mdcore · 23,987 bytesSKILL.mdcore · 23,987 bytesSKILL.mdcore · 23,987 bytesSKILL.mdcore · 23,987 bytesSKILL.mdcore · 23,987 bytesSKILL.mdcore · 23,987 bytesSKILL.mdcore · 23,987 bytesreferences/stripe-mcp-oauth-revocation.mddoc · 3,301 bytesscripts/diagnose-oauth-mcp.pyruns · 7,785 bytes
Read excerpt
# 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.