MCP Reference

Overview

Preflight MCP has one execution path through the running app. The CLI bridge forwards tools/list and tools/call to the same runtime so tool contracts stay aligned.

Tool Catalog (5 Master Tools)

preflight_session

• load, export, reset, health

preflight_diagnose

• validation
• texture (optional target_profile)
• scene_graph
• model_info
• geometry
• schema

preflight_transform

• scale, center, rotate, visibility, revert

preflight_fix

• apply
• texture_convert (input_path, output_path, format, quality, backend, max_dimension, generate_mipmaps, gamut_in, gamut_out)
• apply_all
• plan_create
• plan_execute
• undo

preflight_app

• screenshot, select, control

Texture Remediation Execution Model

• Sandbox-safe app behavior: no CLI subprocess spawn for app-side conversion.
• Execution path: shared in-process interop bridge.
• Capability gating: runtime reports converter capability; unsupported environments return structured unavailability responses.
• Backend selection: automatic | openSource | appleTextureConverter (optional).

Recommended Texture Flow

1. preflight_diagnose(action=texture, target_profile=...)
2. Inspect rule IDs and recommendations
3. preflight_fix(action=texture_convert, backend=automatic|openSource|appleTextureConverter, ...)
4. Re-run preflight_diagnose(action=texture) or full validation