Hyper Agent Integration Kit

Plain-English AI control for the Unreal Editor.

Hyper Agent is a prebuilt Unreal Engine 5.7 editor plugin that lets an AI assistant work inside the editor in real time. It can spawn actors, create Blueprints, wire nodes, build widgets, set up materials, edit assets, and run multi-step workflows locally.

It is not a code generator that only writes text. Hyper Agent drives the Unreal Editor directly through its tool layer.

What You Get

• 510 editor tools across scene editing, Blueprints, UI, animation, materials, AI, level design, diagnostics, workflow automation, and more.
• Built-in in-editor chat panel for working from inside Unreal Editor.
• Local-only tool execution.
• Undo support for editor changes.
• Permission controls for risky operations.
• Project knowledge scanning so the AI can understand Blueprints, structs, enums, gameplay tags, data tables, and related project data.
• Git helpers for status, diff, commit workflows, and source-control aliases.
• Workflow and diagnostic tools, including CVar discovery, runtime state capture, debug draw, spatial scene queries, captures, production audits, localization, media, context memory, command inbox/workflow automation, quarantine helpers, health checks, editor utility helpers, C++ source authoring, and packaging/testing helpers.
• Prebuilt binary for Unreal Engine 5.7 on Windows 64-bit.

How It Works

You
-> Hyper Agent chat panel inside Unreal Editor
-> ACP chat agent (Claude Code, GitHub Copilot, Codex, Gemini, or custom ACP)
-> HyperAgent MCP server
-> Hyper Agent UE plugin
-> Live editor actions

Tool execution stays local. There is no proxy, hosted bridge, or cloud relay for editor tool execution.

Optional HTTP Automation Bridge

The HTTP Automation Bridge is a local HTTP bridge for non-MCP automation clients such as Jenkins, Python scripts, curl checks, and dashboards. It is opt-in and is not used by the existing MCP/chat flow unless you explicitly start it.

Use it when:

• Jenkins or another CI system needs to validate, cook, or package the project.
• A Python script or web dashboard needs status, capabilities, or command results.
• You want a simple curl-based health check.
• An external tool cannot speak MCP but can call localhost HTTP endpoints.

Do not use it for normal in-editor chat. The Unreal chat panel and MCP clients use the standard MCP server flow.

Bridge Files

In packaged builds, look beside the server executable for:

MCPServer/HTTP_BRIDGE_QUICKSTART.md
MCPServer/pipeline_config.example.json

• HTTP_BRIDGE_QUICKSTART.md contains the shortest startup commands.
• pipeline_config.example.json contains project-specific CI stages such as cook, package, archive, and post actions.

Start the Packaged HTTP Bridge

cd PluginsHyperAgentMCPServer
.hyper-agent-server.exe --transport http --port 8765

The bridge binds to 127.0.0.1 only. It writes a per-launch bearer token to MCPServer/bridge/bridge-status.json and stores durable results under MCPServer/bridge/results/.

Useful Endpoints

GET  /health
GET  /status
GET  /capabilities
GET  /describe_all
GET  /pipeline
POST /command
POST /batch
POST /pipeline/run
POST /pipeline/sync
POST /pipeline/compile
POST /pipeline/validate
POST /pipeline/test
POST /pipeline/cook
POST /pipeline/package
POST /pipeline/archive
POST /pipeline/post_actions
GET  /results/latest

The pipeline endpoints are thin CI-friendly aliases. sync, compile, and validate use safe defaults. test requires test_name or test_filter. cook, package, archive, and post_actions are named stages, but expect project-specific commands in the request body.

Project-Specific CI Configuration

For project-specific CI, copy MCPServer/pipeline_config.example.json to MCPServer/pipeline_config.json and fill in the stage commands. Placeholders can be supplied from the request body, including {{path}}, {{files}}, {{platform}}, and any scalar key.

Dry run example:

curl -H "Authorization: Bearer " `

-H "Content-Type: application/json" `

-d "{"stages"":[""compile""