InGame MCP Server

Note: This page presents an overview of the InGame MCP and an explaination of what is a MCP server. If you're already familiar with these basic principles and want to get straight to the point, you can skip this page and go directly there.

InGame MCP Server

InGame MCP Server is a plugin allowing you to embed a MCP server in an Unreal Engine application, making it easy to  control your game or application with a extern MCP Client. The following video shows some of the features enabled with In Game MCP Server, but the possibilities are endless.

(Vidéo de démo ici)

Introduction to MCP (Model Context Protocol)

The Model Context Protocol is an open-source standard designed to standardize how AI models interact with external environments.

Instead of coding specific and rigid integrations for each AI, MCP allows to declare a "context server". The server will then expose:

• Tools: Functions that can be executed by the AI.

• Resources: Data that the AI can read to understand the world.

The AI (the client) reads this list and intelligently decides which tool to use based on the user's request. 

(Shéma de représentation ici)

Key Features of MCP

• The AI discovers your tools and chooses to use them if its reasoning requires it. 

• Architecture based on descriptive JSON Schemas.

• JSON-RPC communication for continuous context exchange. 

• Tool's description red by the AI at runtime to understand its purpose. 

InGame MCP Server Features

As we explained, just like a usual MCP server, InGame MCP Server can register tools and resources.

But the real power of InGame MCP Server is its ability to communicate with Unreal Engine Blueprints. Thanks to this, InGame MCP Server becomes a embeded runtime MCP Server making it possible to interact with the game with a extern MCP Client.