Unreal_mcp and unreal-mcp
These are competing implementations of MCP servers for Unreal Engine control, both offering similar natural language AI integration capabilities but differing in their underlying architecture (native C++ Automation Bridge versus a more general MCP approach).
About Unreal_mcp
ChiR24/Unreal_mcp
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal Engine through the native C++ Automation Bridge plugin. Built with TypeScript and C++.
This project allows AI assistants to directly control Unreal Engine projects. You can instruct an AI assistant, like Claude or Cursor, to perform complex tasks such as spawning actors, editing levels, creating visual effects, or even manipulating animation timelines. The AI assistant acts as the input, and the result is direct changes and actions within your Unreal Engine project, making it ideal for game developers, cinematic artists, and virtual production professionals.
About unreal-mcp
chongdashu/unreal-mcp
Enable AI assistant clients like Cursor, Windsurf and Claude Desktop to control Unreal Engine through natural language using the Model Context Protocol (MCP).
This project allows you to control Unreal Engine using plain English commands through an AI assistant like Claude Desktop or Cursor. You can tell the AI assistant what you want to create, modify, or inspect within your Unreal Engine project, and it will execute those actions. This is for game developers, architects, or anyone building 3D environments in Unreal Engine who wants to speed up their workflow by using natural language instead of manual clicks and code.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work