nick/claudaris
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
code
2026-07-14 21:01:46 +00:00
parent bcd7e012ba
commit c3432b2df4
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/mcp.md
+6 -3
View File
@@ -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 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 something like *"list my Gitea repos"*. Note that a server whose env vars
will show as failed/erroring until you set them — the other servers are are unset still connects — the servers only read them when a tool is
unaffected. 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.