docs: unconfigured MCP servers still connect; failures show at tool-call time

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-14 21:01:46 +00:00
parent bcd7e012ba
commit c3432b2df4
1 changed files with 6 additions and 3 deletions
@@ -73,6 +73,9 @@ claude mcp list      # all three should show as configured
 ```

 Or in a Claude Code session, run `/mcp` to see connection status, and try
-something like *"list my Gitea repos"*. A server whose env vars are unset
-will show as failed/erroring until you set them — the other servers are
-unaffected.
+something like *"list my Gitea repos"*. Note that a server whose env vars
+are unset still connects — the servers only read them when a tool is
+actually called — so a green `/mcp` status doesn't prove the configuration
+is right. Tool calls failing (or Gitea answering about gitea.com instead of
+your instance, its built-in default) is the symptom of missing/wrong env
+vars.