MCP OAuth re-authentication required every few hours (Notion, Atlassian) on Windows

Resolved 💬 3 comments Opened Apr 6, 2026 by dawn-mischewski Closed Apr 10, 2026

Platform

  • Windows 11 Pro (win32), Claude Code CLI
  • Credential storage: Windows Credential Manager

MCP servers affected

  1. mcp__claude_ai_Notion (cloud-hosted, Anthropic-managed OAuth)
  2. mcp__plugin_atlassian_atlassian (plugin-managed OAuth via claude-plugins-official)

Frequency

Re-authentication required every few hours, multiple times per day — even within long-running sessions. Tokens expire mid-work, not just across sessions.

Impact

These are core tools for a PM workflow (product requirements in Notion, engineering tickets in Jira via Atlassian). Re-auth interrupts automated skill chains (/daily-update, /weekly-planning, /end-of-day) that are designed to run with minimal friction. The constant OAuth browser popups break flow and make unattended skill execution impractical.

Expected behavior

OAuth refresh tokens should be stored and used automatically to renew access tokens without user interaction. Tokens should persist across sessions and not expire mid-session.

Actual behavior

Refresh tokens appear to be stored in ~/.claude/.credentials.json but are not used to silently renew expired access tokens. User is prompted to re-authenticate via browser flow every few hours.

Possibly related issues

  • #28256 (Notion refresh tokens not persisting)
  • #19456 (Keychain/credential storage errors)
  • #18442 (tokens expire in idle conversations)

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗