AgentSidekick

Better agent tooling for Unreal Engine

Integration gap · Measured demandOverall 40.4 / 100 DERConfidence Medium DERCalculated

264 public GitHub issues mention "Unreal Engine mcp" (checked 2026-11-21) SRC, while 24 indexed products mention Unreal Engine DER. On the six weighted components it scores 40.4 of 100, confidence Medium, as of 2026-11-21.

Score breakdown

Contribution = weight × component score. The contributions add up to the overall score.

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.2525.00.25 × 25.0 = 6.25Measured
Competition gap0.2053.00.20 × 53.0 = 10.60Measured
Monetisation0.2035.00.20 × 35.0 = 7.00Heuristic
Growth (relative)0.1534.00.15 × 34.0 = 5.10Measured
Feasibility0.1035.00.10 × 35.0 = 3.50Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0040.35 → 40.4

Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.

Confidence: Medium

Rule: Medium when at least 50 GitHub issues mention the integration and at least 10 indexed products mention it; otherwise Low. Nothing is rated High.

What would raise it

  • Medium is the highest level the rules assign. High would need a second, independent demand source (search volume or marketplace installs), which is not connected.

The opportunity

All text in this section is generated by rule from the record. It is a starting point, not research.

Description
Developers are asking for Unreal Engine access from AI agents more than the current supply of well-maintained tools would suggest.DER
Problem
Agents need to read from and act on Unreal Engine. Only some of the existing tools are both documented and actively maintained.DER
Target users
Developers and individuals who use Unreal EngineHEU
Product form
MCP server (optionally bundled as a plugin with skills)HEU
Revenue model
Open source with paid hosting or supportHEU
Complexity
HighHEU
Competition level
HighDER
Subject
Unreal Engine (integration)

Evidence for

2 row(s) from opportunity_evidence.

  • Competition gapMeasuredDERvalue 19

    24 indexed products mention Unreal Engine; 19 of them have a complete record and a repository pushed in the last 180 days.

    /integrations/unreal-engine/

  • DistributionMeasuredDERvalue 37

    37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.

    /platforms/

Evidence against

4 row(s) from opportunity_evidence.

  • DemandMeasuredDERvalue 264

    264 public GitHub issues contain the phrase "Unreal Engine mcp" (checked 2026-11-21); that is the 25th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.

    Source

  • MonetisationHeuristicHEU

    Unreal Engine is not primarily a paid business product. This is a rule of thumb, not revenue data.

  • Growth (relative)MeasuredDERvalue 8

    8 products launched in the last 90 days versus 3 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.

  • FeasibilityHeuristicHEU

    No public API recorded for Unreal Engine; building may need partner access.

    Source

Existing products

All Unreal Engine products

The most notable profiled products mentioning Unreal Engine (up to 8). 24 indexed in total.

unreal-mcp

MCP serverby chongdashuHEU

2.1k GitHub starspushed 1y agolicence unknown

unreal-engine-mcp

MCP serverby ChiR24SRC

1.1k GitHub starspushed todayMIT

UnrealClaude

MCP serverby NatfiiHEU

1.1k GitHub starspushed 4mo agolicence unknown

VibeUE

MCP serverby kevinpbuckleyHEU

844 GitHub starspushed 1d agoMIT

UnrealGenAISupport

MCP serverby prajwalshettydevHEU

686 GitHub starspushed 6mo agoMIT

ue-mcp

MCP serverby db-lyonHEU

513 GitHub starspushed todayMIT

Where it could be distributed

All platforms

37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.

ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more

Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU

Data coverage

Indexed products
24DER
With a full profile
8+DER
Launches, last 90 days
8 vs 3 in the 90 beforeSRC
Demand measured
SRC
Segment calculated
Score calculated

Risks and counterarguments

  • The vendor may ship (or already ships) an official Unreal Engine server, which usually becomes the default.
  • Issue mentions measure developer discussion, not willingness to pay.
  • No public API on record.
  • 264 public GitHub issues contain the phrase "Unreal Engine mcp" (checked 2026-11-21); that is the 25th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.
  • Unreal Engine is not primarily a paid business product. This is a rule of thumb, not revenue data.
  • 8 products launched in the last 90 days versus 3 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.
  • No public API recorded for Unreal Engine; building may need partner access.

Assumptions

What has to be true for the score to mean anything.

  • Mentions of "Unreal Engine mcp" in GitHub issues reflect developers wanting Unreal Engine access from agents.
  • Products that mention the integration in their description or package metadata are the competing supply; ones that do not name it are missed.
  • "Well-maintained" means data completeness ≥ 0.6 and a repository push in the last 180 days.
  • Percentiles compare this integration only with the other integrations tracked, not with the wider market.
  • A platform that documents MCP support can run any MCP server; no pairing has been tested.

How to verify this yourself

  1. Run the demand query on GitHub: https://github.com/search?q=%22Unreal%20Engine%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 264 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
  2. Check the supply on the Unreal Engine page and search the official MCP Registry and the vendor's own app directory for an official server.
  3. Download the record with all evidence: /api/dataset/opportunities.json.

All opportunities · Methodology · Report an error

Page data last updated .