{"version":"2.1.219","anchor":"claude-mcp-list-shows-why-a-server-failed","canonical_anchor":"claude-mcp-list-shows-why-a-server-failed","heading":"claude mcp list shows why a server failed","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/claude-mcp-list-shows-why-a-server-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### `claude mcp list` shows why a server failed\n\nclaude mcp list now tells you why a server failed, like a timeout or HTTP error, not just \"Failed to connect\".\n\n**What**\n\nA failed server is no longer reported as just \"Failed to connect\"; the status line can now say what went wrong.\n\n**Details**\n\n- the per-server status result optionally carries an `issue` field, which the list formatter appends to the status\n- the detail is derived from the error code and `displayDetail`, for example \"request timed out\" or an HTTP code\n- MCP error reporting joins `error` and `displayDetail` into a single sanitised string\n\n**Evidence**\n\n`Failed to connect`\n\n- Area: MCP\n- Names: `claude mcp list`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}