fix-hermes-notion-mcp-oauth-callback-race-windows

What problem does it solve?

This Skill resolves a Windows OAuth callback race where Hermes reports a successful authorization in the browser but still times out or fails to persist the Notion MCP OAuth token, causing repeated authorization prompts.

Core Features & Use Cases

• Diagnoses callback listener timing issues: Identifies whether the local callback server is not listening on 127.0.0.1:<port>/callback when Notion redirects back.
• Guides code-level remediation: Implements the correct operational order by binding the callback server before opening the browser, then using the bound redirect URI for the OAuth request.
• Provides Windows-specific mitigation and verification: Reduces repro failure rate by managing consent tabs and verifying token persistence via the Hermes token directory, not just browser status.
• Use Case: When testing hermes mcp test notion on Windows, you can eliminate “Authorization Successful”-but-not-connected behavior so tool discovery and Notion data access work reliably across runs.

Quick Start

Run the Notion MCP OAuth test on Windows and use the recommended callback-first flow to ensure the redirect URI matches the bound local port and the token is persisted before the command times out.