Claude is missing token in /mcp request upon restarting claude desktop app

### MCP server URL

This issue occurs with every mcp server

### Where does the issue occur?

Other

### Transport used

streamable-http

### Client registration type

Dynamic Client Registration (DCR)

### SSE only: Does your server return the expected status code for POST requests?

Not applicable (my server does not use SSE)

### When did you last reproduce this?

24th april 4:05 PM

### Browser and OS

macOS 26.4.1, Claude 1.3883.0

### Describe the issue

After closing and reopening Claude Desktop, the first /mcp request to an MCP server is sent without the OAuth/auth token — even though the token is still valid and stored. The server responds with 401 Unauthorized. Claude then immediately retries the same request with the token, and it succeeds.
This happens on every app restart.
Expected Behavior
Claude Desktop should include the stored auth token on the first MCP request after restart, avoiding the unnecessary 401 round-trip.

### Issue details

```shell
Steps to Reproduce

Connect to an MCP server that requires auth (token is obtained and working)
Close Claude Desktop completely
Reopen Claude Desktop
Observe the first /mcp request in server logs — it arrives without a token
Server returns 401
Claude retries with the token — succeeds

Impact

Unnecessary 401 error on every restart
Extra latency on first MCP interaction
Noisy server logs / potential rate-limit concerns for MCP server operators

Environment

OS: (fill in: macOS / Windows / Linux + version)
Claude Desktop version: (fill in)
MCP server: (your server name/type, if comfortable sharing)
```

### Expected behavior

Claude Desktop should include the stored auth token on the first MCP request after restart, avoiding the unnecessary 401 round-trip.

### Logs from your server

```shell

```

### Additional context

_No response_