Update from code changes: MCP server connection recovery

[mintlify]

Summary

Document the new recovery paths for broken MCP server connections on AI agents.

Changes

• Add a Recovering a broken connection section to the MCP servers guide covering:
  • Test connection button/menu action that now persists the live-check result (so revoked tokens flip the badge to Reconnect required).
  • Update token modal for bearer-token servers, with pre-save validation so a bad token can't overwrite a working one.
  • Reconnecting OAuth servers, plus the ~5 minute self-heal for abandoned OAuth popups and the always-available Remove / Disconnect escape hatch.
  • Slack agents: the OAuth login prompt is now posted only on the first message of a thread, and once per user + server across threads; disconnecting resets it.

Context

Follows source PRs:

• feat(ai-agents): recover broken MCP connections — rotate bearer tokens + persist status [PROD-8746] lightdash#25298 — recover broken MCP connections (rotate bearer tokens + persist status)
• fix: post Slack MCP OAuth login prompt once per user+server lightdash#25342 — post Slack MCP OAuth login prompt once per user + server
• fix: keep stuck MCP OAuth connection removable and self-healing lightdash#25343 — keep stuck MCP OAuth connections removable and self-healing
• fix: avoid repeated MCP auth prompts lightdash#25372 — avoid repeated MCP auth prompts within a Slack thread
• fix: rename MCP connection action lightdash#25394 — rename MCP connection action to "Test connection"

Update history

• Initial: documented recovery paths (test connection, update token, OAuth self-heal, Slack once-per-user prompt) from feat(ai-agents): recover broken MCP connections — rotate bearer tokens + persist status [PROD-8746] lightdash#25298, fix: post Slack MCP OAuth login prompt once per user+server lightdash#25342, fix: keep stuck MCP OAuth connection removable and self-healing lightdash#25343.
• Follow-up: renamed "Re-test connection" → "Test connection" and clarified that the Slack OAuth login prompt only appears on the first message of a thread, per fix: rename MCP connection action lightdash#25394 and fix: avoid repeated MCP auth prompts lightdash#25372.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
lightdash	🟢 Ready	View Preview	Jul 10, 2026, 12:50 AM

[github-actions]

🤖 Documentation Bot

✅ All checks passed! No issues found.

[mintlify]

Update from code changes updated this PR.

Renamed Re-test connection to Test connection and clarified the Slack OAuth login prompt only appears on a thread's first message.

Source PRs

• lightdash/lightdash#25298 — feat(ai-agents): recover broken MCP connections — rotate bearer tokens + persist status
• lightdash/lightdash#25342 — fix: post Slack MCP OAuth login prompt once per user+server
• lightdash/lightdash#25343 — fix: keep stuck MCP OAuth connection removable and self-healing
• lightdash/lightdash#25394 — fix: rename MCP connection action
• lightdash/lightdash#25372 — fix: avoid repeated MCP auth prompts

[github-actions]

🤖 Documentation Bot

✅ All checks passed! No issues found.