MCP Reference

This page documents the current MCP surface exposed by Preflight.

Overview

Preflight can be used by MCP-compatible clients (for example Codex, Claude Code, or custom automation) through:

1. In-app MCP HTTP bridge (/mcp) exposed by the running app.
2. preflight-mcp CLI, which proxies tool calls to the running app.

The CLI does not maintain a separate tool catalog. It forwards tools/list to the app so both surfaces stay in parity.

Transport Model

• App MCP endpoint: local HTTP bridge with JSON-RPC (tools/list, tools/call).
• CLI endpoint: stdio MCP server that forwards calls to app MCP bridge.
• Execution target: tool execution is performed by the running Preflight app/session.

Current Tool Catalog

Core Diagnostics

• load_file(path)
• get_validation_results()
• get_scene_graph()
• get_model_info()
• get_geometry_breakdown(path?, limit?, sort_by?)
• get_screenshot()

Scene Context + Inspection

• select_prim(path)
• inspect(domain, mode, path?)

Fix Planning + Execution

• create_fix_plan(title, description, steps[])
• preflight_workflow(...) (alias)
• execute_fix_plan_step()
• execute_fix_plan_all()
• undo_last_fix()
• reset_session()

Scale + Export

• scale_model(target_meters|preset)
• export_session(output_path)
• export(output_path) (alias)

UI Controls

• list_gui_actions()
• gui(action)

Recommended Call Sequence

1. load_file(path)
2. get_validation_results()
3. create_fix_plan(...)
4. execute_fix_plan_step() or execute_fix_plan_all()
5. get_validation_results() (verify)
6. export_session(output_path)

Notes

• Some tools have aliases for compatibility; prefer canonical names listed above.
• For sandboxed builds, external file paths may require user-granted access (security-scoped permission flow).
• Source of truth for tool definitions lives in:
  • source/Preflight/PreflightPackage/Sources/AgentModule/AgentTools.swift