Loomle MCP Server

Connect Loomle to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Loomle is an agent-native Unreal Engine integration for reading and changing complex editor objects through SAL, the Structured Agent Language. The loomle mcp server is what makes that connection.

What the server does

• Compact SAL Object Text uses fewer tokens than large generic JSON payloads
• Queries start with summaries and local views instead of downloading an
• Target-relative stable identity paths make returned Nodes, Pins, Graphs,
• Palette and dynamic schema discovery let agents use capabilities that UE
• Dry runs share the real parse, resolve, validate, and plan path before any
• Native compiler and object health diagnostics stay adjacent to the objects

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Target — relative stable identity paths make returned Nodes, Pins, Graphs,
• status — inspect the Client version, update availability, and bound session
• project — inspect project availability and bind this MCP session to one
• sal_query — execute one self-contained SAL Query Text
• sal_patch — execute one ordered SAL Patch Text
• sal_schema — discover the resident SAL guide and the active interface cards
• agent_skill — discover and load MCP-managed Loomle workflow Skills without
• editor — observe the current Unreal interaction with empty arguments, or
• Website — https://loomle.ai/
• Quickstart — https://loomle.ai/quickstart.html
• Releases — https://github.com/loomle/loomle/releases
• Package — Contents

Installation

The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Loomle's toolset — Target, status, project and 11 more — is a fair guide to whether it matches your workflow. It is maintained by loomle; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Loomle.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.