Claude Code AI doesn't know MCP servers are configured in ~/.claude.json

Problem

When users ask Claude Code for help debugging MCP server connectivity or configuration issues, the AI assistant repeatedly looks in the wrong locations for MCP server definitions.

Actual behavior

The AI looks for MCP server definitions in:

• ~/.claude/settings.json
• Project-level .claude/settings.json

This leads to incorrect debugging paths, unnecessary file reads, and user confusion.

Expected behavior

The AI should know that the canonical location for user-level MCP server configuration is ~/.claude.json (the mcpServers key). When a user asks to debug why an MCP server isn't connecting, or asks where MCP servers are configured, the AI should go directly to ~/.claude.json.

Example scenario

User: "Why isn't my MCP server connecting?"

Claude Code currently reads ~/.claude/settings.json, finds no mcpServers key, then checks project-level .claude/settings.json, and goes on an exploratory tangent — instead of immediately opening ~/.claude.json where the server definitions actually live.

Suggestion

The system prompt or model knowledge base should explicitly document that:

• ~/.claude.json → mcpServers key is the canonical user-level MCP server config (added via claude mcp add --scope user)
• ~/.claude/settings.json does not contain MCP server definitions

This is related to #32398, but that issue's expected behavior section incorrectly identifies ~/.mcp.json and ~/.claude/settings.json as the canonical locations — the actual correct location is ~/.claude.json.