From c3432b2df46c7ee0416b067627aa5e0827ac8ce0 Mon Sep 17 00:00:00 2001 From: code Date: Tue, 14 Jul 2026 21:01:46 +0000 Subject: [PATCH] docs: unconfigured MCP servers still connect; failures show at tool-call time Co-Authored-By: Claude Fable 5 --- docs/mcp.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/mcp.md b/docs/mcp.md index 4162926..f93b19c 100644 --- a/docs/mcp.md +++ b/docs/mcp.md @@ -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.