LOOMLE
About
Unreal Engine MCP server for Claude Code, Codex, and AI agents to inspect and edit live UE projects through Blueprint, Material, PCG, UMG, asset, context, and diagnostics tools.
Details
- Author
- loomle
- Categories
- Developer Tools, Other, AI
Jump to
Setup
Install LOOMLE in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/loomle/loomle
Follow the installation instructions in the repository README, then restart your MCP client.
Loomle is an agent-native Unreal Engine integration for reading and changing complex editor objects through SAL, the Structured Agent Language.
SAL turns Blueprint graphs, Widget trees, Class reflection, Assets, and other non-text UE state into compact, ordered text that both people and agents can read, copy, discuss, and patch. It stays faithful to UE: native paths, types, field names, values, palette actions, compiler diagnostics, and editor semantics remain native instead of being replaced by a parallel JSON model.
Text code already gives agents precise search, references, diffs, and edits. Unreal assets do not. Loomle supplies that missing text workflow while keeping the editor and UE APIs as the source of truth.
- Compact SAL Object Text uses fewer tokens than large generic JSON payloads.
- Queries start with summaries and local views instead of downloading an entire graph.
- Target-relative stable identity paths make returned Nodes, Pins, Graphs, Widgets, and Blueprint objects safe to follow up without kind namespaces.
- Palette and dynamic schema discovery let agents use capabilities that UE actually exposes instead of guessing constructors or fields.
- Dry runs share the real parse, resolve, validate, and plan path before any mutation is applied.
- Native compiler and object health diagnostics stay adjacent to the objects they describe.
The standalone Client exposes eight MCP tools:
- status: inspect the Client version, update availability, and bound session and Bridge health.
- project: inspect project availability and bind this MCP session to one Unreal project.
- 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 a separate agent-specific installation.
- editor: observe the current Unreal interaction with empty arguments, or open, focus, and close an exact Blueprint or Graph from canonical SAL Target Text.
- python: run unrestricted Unreal Editor Python only as a fallback for capabilities not covered by a structured Loomle interface, and poll an execution only when the initial result supplies a continuation.
The current public SAL modules are Asset, Blueprint, Class, Graph, StateTree, and Widget. They cover Asset Registry discovery, Blueprint declarations and components, Class reflection and defaults, graph-local flow and mutation, StateTree hierarchy and bindings, Widget trees, factual reference queries, compilation, save, and editor context.
door = target { domain: blueprint, asset: "/Game/Blueprints/BP_Door.BP_Door" } query door summary
Usesal_schema({})for the active module index andsal_schema({ module: "graph" })for one exact interface card. Supported exact reads and Palette Entries provide dynamic discovery withwith schema; each interface card states the exact subjects that accept it.
The latest stable Loomle release is available fromGitHub Releasesfor Unreal Engine 5.7 and 5.8. Choose the package matching the installed engine version:
These stable filenames always resolve through the latest final GitHub Release. That release also retains immutable, versioned copies of both archives.
The complete archive contains both native targets and their matching Clients:
LoomleBridge/ Source/ Resources/ Loomle/ <platform-arch>/ loomle(.exe)
The executable underResources/Loomleis the self-contained SAL Client. It requires no separate Python,uv, Node.js, global Loomle install, or project-local Client.
Before upgrading from 0.6, close Unreal Editor and remove or move the old<Project>/Plugins/LoomleBridgedirectory. A same-named project plugin takes precedence over the new engine plugin and would keep loading 0.6.
Extract the complete archive, then copy theLoomleBridgedirectory to:
<UE_5.7-or-5.8>/Engine/Plugins/Marketplace/LoomleBridge
EnableLoomleBridge, restart Unreal Editor, and configure an MCP server namedloomleto launch the bundled Client with the argumentmcp:
macOS: LoomleBridge/Resources/Loomle/darwin-arm64/loomle Windows: LoomleBridge/Resources/Loomle/win32-x64/loomle.exe
Seehttps://loomle.ai/quickstart.htmlfor a complete first query and patch.
Agent / MCP host -> bundled Loomle Client (stdio MCP + SAL) -> local runtime record -> LoomleBridge inside Unreal Editor -> UE 5.7 or 5.8 editor APIs and object model
The Client discovers live Bridge instances through~/.loomle/state/runtimes. This directory is runtime discovery state, not a global installation. Each MCP session keeps one sticky project binding and validates that project's current Editor with a short live health probe. If the bound project is offline, Loomle reports that state and never falls through to another online project. Useproject({})to inspect candidates and bind or switch explicitly when needed.
The repository has four current product boundaries:
- sal/: language parser, normalized model, schemas, and TypeScript SDK.
- interfaces/: resident guide and static UE interface cards.
- client/: standalone MCP Client.
- engine/LoomleBridge/: Unreal Editor plugin.
Install workspace dependencies and run the TypeScript test suite:
Build and test the native Client for the current supported runner:
npm run build:executable npm run test:executable
Run the complete Loomle UE Automation category against a same-commit development plugin compiled with the native tests:
npm run test:ue-automation -- \ --ue-root <UE-root> \ --project-template tests/fixtures/ue/LoomleTestHost \ --plugin-dir <compiled-same-commit-test-plugin> \ --output-dir <new-artifact-directory> \ --target darwin-arm64
The output directory must not already exist. Raw plugin source is not a runnable candidate. The final release archive intentionally excludes native test code, so it is not the complete Automation candidate.
Run the small packaged Client-to-UE workflow against the exact audited release archive and its bundled Client:
npm run test:packaged-e2e -- \ --ue-root <UE-root> \ --project-template tests/fixtures/ue/LoomleTestHost \ --plugin-archive <final-release-candidate.zip> \ --output-dir <new-artifact-directory> \ --target darwin-arm64
Release assembly consumes only the canonical program at.tmp/client/<platform-arch>/loomle(.exe)and combines it with the Bridge source plugin. Seepackaging/client/andpackaging/fab/for the artifact contracts.
- Website:https://loomle.ai/
- Install:https://loomle.ai/install.html
- Quickstart:https://loomle.ai/quickstart.html
- Interface overview:https://loomle.ai/tools/
- Releases:https://github.com/loomle/loomle/releases
Repository and product design documents live underdocs/; canonical SAL and UE interface contracts live undersal/docs/andinterfaces/. Loomle 0.6 source and documents remain available from the0.6branch, its release tags, and repository history;maincontains only the current design and code.
Loomle is open source under the MIT License. SeeLICENSE.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
next-devtools-mcp is a MCP server that provides Next.js development tools and utilities for AI coding assistants like Claude and Cursor.
A demonstration server for ActionKit, providing access to Slack actions via Claude Desktop.
MCP server that lets Claude Code agents delegate tasks to agents in other project directories, with parallel dispatch, sessions, and async jobs.
Anchor Browser (https://anchorbrowser.io) is secure infrastructure for computer-use agents — stealth cloud browsers, authentication, captcha bypass, and a hosted MCP server for Cursor, Claude, and Windsurf.
Open-source Claude Code plugin replacing Read/Grep/Edit/Bash with token-efficient versions. Independently benchmarked at 57% token reduction on real codebases. 40 MCP tools.
Connects Blender to Claude AI via the Model Context Protocol (MCP), enabling direct interaction and control for prompt-assisted 3D modeling, scene creation, and manipulation.
Context-optimized security plugin for Claude Code that builds architecture maps and redacts secrets.
Charon gives AI clients scoped, auditable access to Lethe memory. connect to Chatgpt or Claude to store memories locally.
Score CLAUDE.md/AGENTS.md, validate clarx-manifest.json, generate CI workflows, and pull repo scan findings into Cursor, Claude, or Grok.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
