claude-code - 💡(How to fix) Fix Phantom '1 failed' MCP server when cloud connectors disabled via feature flag [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49592Fetched 2026-04-17 08:36:47
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

When tengu_claudeai_mcp_connectors is set to false in ~/.claude.json to disable the claude.ai MCP connectors (Gmail, Google Calendar, Google Drive), /status still reports "1 failed" MCP server. However, /mcp shows no failed servers — all listed servers are connected and healthy.

Root Cause

When tengu_claudeai_mcp_connectors is set to false in ~/.claude.json to disable the claude.ai MCP connectors (Gmail, Google Calendar, Google Drive), /status still reports "1 failed" MCP server. However, /mcp shows no failed servers — all listed servers are connected and healthy.

RAW_BUFFERClick to expand / collapse

Description

When tengu_claudeai_mcp_connectors is set to false in ~/.claude.json to disable the claude.ai MCP connectors (Gmail, Google Calendar, Google Drive), /status still reports "1 failed" MCP server. However, /mcp shows no failed servers — all listed servers are connected and healthy.

Steps to reproduce

  1. Set tengu_claudeai_mcp_connectors to false in ~/.claude.json
  2. Start Claude Code
  3. Run /status — shows "X connected, 1 failed"
  4. Run /mcp — no failed servers listed, all servers show connected

Expected behavior

/status should show 0 failed servers when all visible MCP servers are connected.

Environment

  • Claude Code 2.1.112
  • macOS (Apple Silicon)
  • Native install (~/.local/bin/claude)

extent analysis

TL;DR

The issue may be resolved by investigating the discrepancy between the /status and /mcp endpoints when tengu_claudeai_mcp_connectors is set to false.

Guidance

  • Verify that the tengu_claudeai_mcp_connectors setting is correctly applied by checking the Claude Code configuration and logs.
  • Compare the output of /status and /mcp to identify any differences in the reported server status.
  • Check if there are any hidden or non-visible MCP servers that may be causing the "1 failed" report in /status.
  • Investigate the Claude Code documentation to see if there are any known issues or limitations related to the tengu_claudeai_mcp_connectors setting.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be specific to the Claude Code version (2.1.112) or the macOS environment, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: temporarily enable tengu_claudeai_mcp_connectors to see if the issue persists, and then disable it again to verify if the problem is related to the setting. This will help to isolate the cause of the discrepancy between /status and /mcp.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

/status should show 0 failed servers when all visible MCP servers are connected.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING