Cannot initialize MCP servers after reboot

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.4.1 (24E263)

### Expected behaviour

$ q chat

And the MCP servers should be properly initialized. Amazon Q start chatting.

### Actual behaviour

> q chat
To learn more about MCP safety, see https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-mcp-security.html
⚠ amzn_mcp has the following warning:
The following tool names are changed:
- amzn_mcp___slack-send-message -> amzn_mcp___slacksendmessage
⠧ 1 of 2 mcp servers initialized
⠋
⠹
⠹
✗ mcp_atlassian has failed to load:
- Operation timed out: recv for initialize
- run with Q_LOG_LEVEL=trace and see $TMPDIR/qlog for detail
✗ 1 of 2 mcp servers initialized

Welcome to

█████╗ ███╗ ███╗ █████╗ ███████╗ ██████╗ ███╗ ██╗ ██████╗
██╔══██╗████╗ ████║██╔══██╗╚══███╔╝██╔═══██╗████╗ ██║ ██╔═══██╗
███████║██╔████╔██║███████║ ███╔╝ ██║ ██║██╔██╗ ██║ ██║ ██║
██╔══██║██║╚██╔╝██║██╔══██║ ███╔╝ ██║ ██║██║╚██╗██║ ██║▄▄ ██║
██║ ██║██║ ╚═╝ ██║██║ ██║███████╗╚██████╔╝██║ ╚████║ ╚██████╔╝
╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝╚══════╝ ╚═════╝ ╚═╝ ╚═══╝ ╚══▀▀═╝

╭───────────────────────── Did you know? ─────────────────────────╮
│ │
│ You can enable custom tools with MCP servers. Learn │
│ more with /help │
│ │
╰─────────────────────────────────────────────────────────────────╯

/help all commands • ctrl + j new lines • ctrl + k fuzzy search
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

### Steps to reproduce

After I rebooted my mac, I cannot initialize the MCP servers ecery time I tried to run "q chat"

### Environment

```yaml

[q-details]
version = "1.9.1"
hash = "5d2c2807cab9bc6c9dc5fcd05f92c7a979e8a4f7"
date = "2025-04-29T06:22:42.917989Z (10d ago)"
variant = "full"

[system-info]
os = "macOS 15.4.1 (24E263)"
chip = "Apple M4 Pro"
total-cores = 14
memory = "48.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/opt/homebrew/Cellar/fish/4.0.1/bin/fish"
shell-version = "4.0.1"
terminal = "macOS"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/.toolbox/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Applications/Wireshark.app/Contents/MacOS:/Users/USER/.local/bin:/Users/USER/.local/bin:/Users/USER/.toolbox/bin"
QTERM_SESSION_ID = "7308e7eb5f6f42e5b7ded735b4d26087"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.9.1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"
```

Riproduci il problema con q chat dopo un riavvio, quindi esegui q doctor e q restart. Abilita Q_LOG_LEVEL=trace e ispeziona $TMPDIR/qlog, concentrandoti sul timeout di inizializzazione di mcp_atlassian. Il lavoro è completato quando entrambi i server MCP vengono inizializzati correttamente e q chat raggiunge la sessione normale senza l’avviso.

Scritto dal modello di indicizzazione a partire dal testo della issue.