notion-mcp-oauth-windows-self-auth

Automate Notion MCP OAuth authorization on Windows via Edge/CDP browser harness.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Pans0020/opencode-skills --skill notion-mcp-oauth-windows-self-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notion-mcp-oauth-windows-self-auth
Source: https://github.com/Pans0020/opencode-skills/tree/main/notion-mcp-oauth-windows-self-auth
Command: npx skills add https://github.com/Pans0020/opencode-skills --skill notion-mcp-oauth-windows-self-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the need for you to manually complete Notion MCP OAuth in a browser when your Windows Hermes agent needs authorization and tools aren’t yet available.

Core Features & Use Cases

  • Browser-harness OAuth automation (Edge/CDP): Clears stale authorization tabs, runs the OAuth flow, and interacts with the consent page via DOM rather than fragile coordinates.
  • Correct callback verification: Keeps the OAuth test process alive so the local 127.0.0.1 callback listener remains ready, then validates success by running the MCP test again instead of trusting the browser page.
  • Post-auth MCP tool validation & fallback: Confirms token persistence in the Hermes token directory and, if tool discovery isn’t reflected in the current agent tool list, uses Hermes’ native MCP client helper to perform Notion operations.

Quick Start

Use the notion-mcp-oauth-windows-self-auth skill when you run Hermes and receive an authorization-required status for Notion MCP on Windows.

Frequently Asked Questions about notion-mcp-oauth-windows-self-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Notion MCP OAuth authorization on Windows when the token is missing or expired?

Notion MCP OAuth authorization on Windows can be automated using an Edge/CDP browser harness that runs the consent flow via DOM interaction and validates the localhost callback. This clears stale tabs and verifies token persistence without manual browser input.

Why does my Notion MCP callback fail on localhost when the test listener closes?

Notion MCP callback verification fails if the local test listener process terminates before the OAuth redirect arrives. Keeping the hermes mcp test process alive ensures the 127.0.0.1 callback listener remains ready to receive and validate the authorization token.

What is the best way to validate Notion MCP tool availability after completing OAuth on Windows?

Validating Notion MCP tool availability after OAuth requires running hermes mcp test notion to confirm token persistence. If tool discovery is not reflected in the agent tool list, Hermes' native MCP client helper can execute Notion operations as a fallback.

Does this Notion MCP authentication method require manual browser interaction on Windows?

No, Notion MCP authentication does not require manual browser interaction because the Edge/CDP harness interacts with the consent page through DOM elements rather than screen coordinates. This approach removes the need for manual clicks during the authorization flow.

Can I use Edge CDP to handle stale OAuth tabs before running the Notion MCP authorization flow?

Yes, Edge CDP can be used to perform stale-tab cleanup before running the Notion MCP authorization flow. Clearing old authorization tabs ensures the automated browser harness opens a fresh consent page without conflicting session state.

What should I do if Notion MCP tools are unavailable after OAuth token persistence on Windows?

If Notion MCP tools are unavailable after OAuth token persistence, use Hermes' native MCP client helper to perform Notion operations directly. This fallback ensures functionality when tool discovery is not immediately reflected in the current agent tool list.