List available monitors.

Use this first when the caller does not know which monitor index to target. index=0 is the virtual full desktop, index>=1 targets a specific monitor.

Capture one screenshot in a single call.

Prefer this tool for small/medium payloads when a one-shot response is desired. For larger payloads or robust transport, use the session flow: start_screenshot_capture -> get_screenshot_manifest -> get_screenshot_chunk -> release_screenshot_capture.

Args: monitor_index: 0 captures the virtual full desktop, 1..N capture a specific monitor. image_format: png or jpeg. max_width: optional resize target width while preserving aspect ratio. quality: JPEG quality in [1, 100]. Ignored for PNG. response_mode: 'base64' (default), 'image' (native MCP image block), or 'auto' (resolved from SCREEN_MCP_CAPTURE_RESPONSE_MODE env var).

Capture a timeline in a single call.

Prefer this tool for short timelines when a one-shot JSON payload is acceptable. For larger timeline payloads or safer transport, use the session flow: start_timeline_capture -> get_timeline_manifest -> get_timeline_chunk -> release_timeline_capture.

• Max duration is enforced by source constant TIMELINE_MAX_DURATION_SECONDS.

• Capture rate is fixed by source constant TIMELINE_FPS (images/second).

• Output is optimized for temporal reasoning by an LLM.

Capture a timeline and store it in a temporary chunked session.

Use this as step 1 of the chunked timeline flow. Next calls should be: get_timeline_manifest, then all get_timeline_chunk, then release_timeline_capture.

Return timeline session metadata without the full payload.

Use this as step 2 after start_timeline_capture to discover total_chunks and validate integrity metadata.

Return one JSON text chunk for a timeline session.

Use this after get_timeline_manifest; fetch chunks from chunk_index=0 to total_chunks-1 in order. Concatenate chunk_text values to reconstruct the full timeline JSON.

Release a timeline session and free memory.

Call this after reading all required chunks.

Capture a screenshot and store it in a temporary server-side session.

Use this as step 1 of the chunked screenshot flow. Next calls should be: get_screenshot_manifest, then all get_screenshot_chunk, then release_screenshot_capture.

Return screenshot session metadata and an ASCII preview.

Use this as step 2 after start_screenshot_capture to discover total_chunks and preview content.

Return one base64 chunk for a screenshot session.

Fetch chunks from chunk_index=0 to total_chunks-1 and concatenate chunk_base64.

Release a screenshot session and free memory.

Call this after reading all required chunks.