MCP server remains stuck in Starting state after startup failure

## Type of Bug

Bug

## Description

When an MCP server fails during startup, the MCP management page can leave the server in a `Starting` state indefinitely. Other UI surfaces, including the JSON/configuration view, correctly reflect that the server has errored.

This makes the MCP page misleading and prevents users from understanding that startup has already failed.

## Steps to Reproduce

1. Configure an MCP server that fails to start.
2. Open the MCP management page.
3. Observe the server status after the startup failure.
4. Compare it with the status shown in the JSON/configuration view.

## Expected Behavior

The MCP management page transitions the server out of `Starting` and shows its error state once startup fails.

## Actual Behavior

The MCP management page remains in `Starting` indefinitely, while the JSON/configuration view correctly shows the error.

## Screenshots