Loomle MCP for Unreal

Load a Loomle Agent Skill when the task matches its description. Call with no arguments to list resident Skills or with one exact name to load its complete instructions and Markdown references. Resident Skills: - debug-unreal-pie-with-python: Control and debug one in-process Unreal Engine Play In Editor or Simulate session through Loomle Python after applying the use-unreal-python safety workflow. Use when reproducing gameplay, querying runtime Actors or components, invoking gameplay APIs, checking state across frames, or managing PIE start and stop. - format-unreal-blueprints: Format and audit Unreal Engine Blueprint K2 graphs through Loomle using exact live node and pin geometry. Use when arranging selected Blueprint nodes, repairing spaghetti, choosing compact Helixing versus left-side data layout, straightening execution flow, separating branches, or evaluating whether a graph has near-human visual quality. - use-unreal-python: Use Loomle's unrestricted Unreal Python fallback safely when no structured Loomle interface covers the required Unreal Editor capability. Apply live context checks, capability selection, API introspection, idempotent mutations, exact continuation polling, partial-state recovery, explicit persistence, and independent result verification.

Observe or control the Unreal Blueprint Editor. Call with no arguments for current context, or use open/close with one bare canonical SAL Blueprint or Graph Target expression.

Inspect Loomle projects or bind this MCP session to one project. Call with no arguments to see the binding and candidates; pass projectId or projectRoot to bind. Binding is sticky, survives Editor restarts, and never falls through to another project while offline.

Run Python in the bound Editor when no Loomle interface covers the capability. Before run, load use-unreal-python; for PIE also load debug-unreal-pie-with-python. Poll exactly; never replay. sal.object(value) marks UObjects for canonical projection. No dry run, rollback, cancellation, idempotency.

Validate or modify Unreal Engine objects with one ordered SAL Patch Text. The first result block is canonical SAL Result Text; metadata and diagnostics use later blocks. Use 'dry run' before risky edits.

Read Unreal Engine objects with one self-contained SAL Query Text. The first text block is canonical SAL Result Text; diagnostics use later text blocks.

# SAL SAL is Loomle's line-oriented language for reading and changing Unreal Engine objects. It keeps UE names, native paths, enum values, property types, and editor behavior intact. ## MCP Calls - `status({})` reports Client, session, and Bridge health. - `project({})` reports project binding and candidates. - `project({ projectId: "<id>" })` binds the session to one project. - `sal_query({ text })` executes one Query Text. - `sal_patch({ text })` executes one ordered Patch Text. - `sal_schema({})` lists the nine active Domain interface cards. - `sal_schema({ module: "graph" })` returns one static card. - `agent_skill({})` lists resident Loomle workflow Skills. - `agent_skill({ name: "format-unreal-blueprints" })` loads one Skill before performing a matching specialized workflow. - `editor({})` returns the user's current UE context as SAL Result Text. - `editor({ operation: "open" | "close", target })` idempotently controls one exact Blueprint Editor or Graph document. `target` is one bare canonical SAL Target expression encoded as the JSON string value. - `python({ operation: "run", script })` is the unrestricted Unreal Python fallback when no structured Loomle interface covers the task. The script defines synchronous `run()` and returns a JSON-compatible dictionary. - If Python returns `status: "running"`, call `python` with the exact `poll` continuation it supplies. Never replay the original script. The tool-call wrapper is not SAL syntax. ## Project Binding One Loomle MCP session operates on one UE project. Start with `status({})`. If the session is unbound, call `project({})`, copy one returned `projectId`, and bind it with `project({ projectId: "<id>" })`. The binding is sticky: Loomle does not fall through to another online project merely because the selected project is offline or its Editor restarts. `sal_schema` remains available without an online project because the resident guide and Domain cards are local. ## Four Separate Concepts…

Inspect Loomle Client and update status plus the bound session and Bridge health. Call once before the first Loomle operation in a task.