Notion MCP token invalidated after context compaction, requires re-authorization every session

Summary

After a conversation context compaction occurs, the Notion MCP server token is invalidated and requires re-authorization, even though the OAuth token itself should still be valid. Previously, the Notion integration token persisted correctly across multiple sessions and conversations without needing re-authorization.

Steps to Reproduce

1. Authorize Notion MCP integration in Claude Code
2. Use Notion MCP tools (e.g., notion-fetch) successfully within a session
3. Continue a long conversation until context compaction occurs (or start a new session after compaction)
4. Attempt to use any Notion MCP tool
5. Receive error: MCP server "notion" requires re-authorization (token expired)

Expected Behavior

Notion MCP token should persist across sessions and survive context compaction. Re-authorization should only be needed when the OAuth token genuinely expires or is explicitly revoked.

Actual Behavior

Token is invalidated after context compaction, requiring re-authorization on every new session or after any compaction event.

Environment

• Platform: macOS (darwin 24.4.0)
• Shell: zsh