diff --git a/docs/inspector/guided-oauth.mdx b/docs/inspector/guided-oauth.mdx
index f9400707b..4fde81203 100644
--- a/docs/inspector/guided-oauth.mdx
+++ b/docs/inspector/guided-oauth.mdx
@@ -38,3 +38,13 @@ To begin debugging OAuth flows:
 5. **Start Testing** - Click **Continue** to begin the OAuth flow
 
 The debugger will guide you through each step of the OAuth handshake, providing real-time feedback and educational context.
+
+## Navigating to the OAuth Debugger from the logger
+
+When an OAuth error appears in the request log, a **Continue in OAuth Debugger** button is shown on hover for that log row. Clicking it switches the selected server to the one that produced the error and deep-links directly to the OAuth Debugger (`#oauth-flow`), so you can investigate the failure without manually locating the right server.
+
+## Reconnecting OAuth servers
+
+The enable/connect toggle on a server card or detail modal reuses existing credentials only — it will not launch a new OAuth consent screen. If the existing tokens are expired or missing and a fresh consent flow is required, the toggle reports a re-authentication error instead of redirecting you to the authorization server.
+
+To start a full OAuth flow, use the explicit **Reconnect** button on the server card or detail modal. This is the only path that will open the OAuth consent screen when new credentials are needed.
diff --git a/docs/troubleshooting/common-errors.mdx b/docs/troubleshooting/common-errors.mdx
index af6307990..9d437470e 100644
--- a/docs/troubleshooting/common-errors.mdx
+++ b/docs/troubleshooting/common-errors.mdx
@@ -50,6 +50,12 @@ If you're seeing **401 Unauthorized** errors when trying to connect to your serv
   process and identify where things might be going wrong.
 </Info>
 
+### Toggle shows a re-authentication error for an OAuth server
+
+The enable/connect toggle on a server card or detail modal reuses existing credentials only. If your tokens are expired or missing, the toggle will report a re-authentication error rather than opening the OAuth consent screen.
+
+**Solution:** Use the **Reconnect** button on the server card or detail modal to start a full OAuth flow and obtain new credentials. The toggle is intentionally non-interactive for OAuth to avoid unexpected browser redirects.
+
 ### Common Configuration Mistakes
 
 - Missing required environment variables