product: assert audience: test-developer, operator, ai-assistant authority: normative

MCP Tools — Live Events

Tools for real-time test progress monitoring via SignalR. The MCP server maintains a persistent hub connection and buffers up to 100 events per type.

For full architecture, polling workflow, and buffer-limit guidance see live-events.md.

All tool responses include a top-level station field containing the StationLabel configured for this server instance.

See also: tools-reference.md for the full tool index.

connect_live_events

Opens (or re-establishes) the SignalR connection to the station hub. Safe to call multiple times — reconnects only when not already connected.

Returns: connected (bool), message (string)

Calls: HubConnectionBuilder → /testExecutionHub

poll_test_progress

Drains all events buffered since the last call. Returns immediately with empty arrays if no new events have arrived. Call every 1–5 seconds while a test is running.

Returns: connected (bool), statusEvents[] (each: executionId, status, verdict), stepEvents[] (each: executionId, stepExecutionId, stepName, currentStep, totalSteps - the position within the sequence running the step, so it restarts inside a sub-sequence; overallStep, overallTotalSteps, overallProgress (0..1) - the test's own top-level progress, a sub-sequence counting as its calling step; depth (0 = top level), parentStepExecutionId (the step that called the sub-sequence) and subSequence (its name). The overall and nesting fields are null from a station older than 2.7.0), packageEvents[], pendingPrompts[] — every operator prompt the station is blocked on right now, in the shape get_pending_prompt returns. Read from the station on every poll rather than from the event stream, so a prompt raised before you connected is still listed. Answer with answer_prompt.

Calls: in-memory drain for the event arrays; GET /api/testexecution/prompts for pendingPrompts