mcp-stub-to-ground-truth

An empty MCP server list usually occurs when the control_request flow is stubbed or broken, causing mcp_status to drop. Tracing the request/response schema in extension.js and cli.js helps identify where the stubbing happens so you can implement the correct fetch logic.

Fixing stuck spinners and missing tool outputs requires replacing stubbed MCP control_request handlers with ground-truth implementations. This enforces bidirectional control planes and channel/session correctness, validated by checking log files for dropped requests.

To replace stubbed MCP control requests, analyze the request/response schemas, identify placeholder logic, and implement bidirectional control planes aligned to extension.js and cli.js. Validate the new ground-truth logic using log files to ensure channel and session correctness.

Stubbed MCP control_request flows break UI behavior when placeholder logic fails to enforce channel and session correctness. Without ground-truth implementations aligned to extension.js and cli.js, the UI cannot fetch server lists or display tool outputs properly.

Yes, log files are required to validate MCP control request fixes and ensure channel/session correctness. They provide the trace data needed to confirm that bidirectional control planes and ground-truth implementations are functioning as intended.