Enginegate

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Gateway to a running Unreal Editor: search, describe, execute, and configure capabilities.

VerifiedSTDIODesktop only

Overview

Enginegate's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Enginegate in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

enginegate

enginegate gives an agent a single doorway into a running Unreal Editor. Instead of a long list of editor tools, it exposes one gateway tool, unreal, with four operations: search the editor's capabilities in plain words, read one capability's contract before using it, execute a capability, and configure which capability groups are enabled.

Every call is forwarded to the editor's own local MCP endpoint, so enginegate only works while an editor with that endpoint is running. When it is not, calls come back as errors carrying the underlying connection problem — enginegate never invents an editor result.

Install

bash
npx @reneturcios/enginegate call '{"operation":"search","query":"spawn actor"}'

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/enginegate

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

Configuration

Environment variableMeaning
UNREAL_MCP_URLThe editor's MCP endpoint. Default: http://127.0.0.1:3000/mcp
MCP_AUTOMATION_CAPABILITY_TOKENWhen set, sent on every forwarded call as the X-MCP-Capability-Token header.

CLI

bash
# Search capabilities in plain wordsenginegate call '{"operation":"search","query":"spawn actor"}'
# Read one internal tool's contractenginegate call '{"operation":"describe","tool":"control_actor"}'
# Execute a capability by tool + action, or by capability idenginegate call '{"operation":"execute","tool":"control_actor","action":"spawn","params":{"class":"PointLight"}}'enginegate call '{"operation":"execute","capability":"control_actor.spawn","params":{"class":"PointLight"}}'
# Configure capability groupsenginegate call '{"operation":"configure","tool":"control_actor","params":{"enabled":true}}'
enginegate --version

Exit codes: 0 on success, 1 when a call fails validation or the editor cannot be reached or returns an error, 2 for usage errors.

Argument requirements are checked before anything is forwarded, and the error names the missing field:

  • search requires query
  • describe requires tool
  • execute requires tool + action, or capability
  • configure requires tool or params

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/enginegate mcp

MCP client configuration:

json
{  "mcpServers": {    "enginegate": {      "command": "npx",      "args": ["-y", "@reneturcios/enginegate", "mcp"]    }  }}

Tools

ToolInputWhat it does
unrealoperation (required; one of search, describe, execute, configure), plus per-operation fields: query, tool, action, capability, params, consentForwards the call to the running editor's gateway. describe returns a capability's contract — including a consent grant for destructive capabilities, which must be passed back as consent to execute them.

Forwarded calls are JSON-RPC tools/call requests for the tool name unreal. The editor endpoint may answer with a plain JSON body or a server-sent-events stream; both are parsed, and the editor's own result text (and error flag) is what the caller receives.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no networknpm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit 9fc7b08

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts