Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/davidbuenov/dbv-mcp-server/llms.txt

Use this file to discover all available pages before exploring further.

Follow these steps to enable the required Unreal Engine plugins, install the Python proxy dependencies, and make your first live MCP tool call from the browser.
1

Enable Unreal Engine plugins

Open your .uproject file in a text editor and add the following plugins to the Plugins array. All seven entries are needed for the full toolset surface; see Requirements for which ones are optional.
{
  "Plugins": [
    { "Name": "ModelContextProtocol",    "Enabled": true },
    { "Name": "ToolsetRegistry",         "Enabled": true },
    { "Name": "MCPClientToolset",        "Enabled": true },
    { "Name": "PythonScriptPlugin",      "Enabled": true },
    { "Name": "EditorToolset",           "Enabled": true },
    { "Name": "AutomationTestToolset",   "Enabled": true },
    { "Name": "SlateInspectorToolset",   "Enabled": true }
  ]
}
Then enable Auto Start Server so the MCP server starts with the editor:
  1. In the Unreal Editor, go to Edit → Editor Preferences.
  2. Search for Model Context Protocol.
  3. Toggle Auto Start Server to Enabled.
Restart the editor. Unreal’s built-in MCP server will now listen on http://localhost:8000/mcp.
2

Install Python dependencies

The proxy server requires three packages. The included start scripts (start.sh / start.cmd) launch server.py using a local virtual environment at ./venv/, so create and activate the venv first, then install the dependencies inside it:macOS / Linux:
python3 -m venv venv
source venv/bin/activate
pip install fastapi uvicorn httpx
Windows:
python -m venv venv
venv\Scripts\activate
pip install fastapi uvicorn httpx
Those three packages — fastapi, uvicorn, and httpx — are the complete set of runtime dependencies for server.py.
3

Start the proxy server

Use the included platform-specific start scripts from the project root. They launch server.py in the background and open the web client automatically.macOS / Linux:
chmod +x start.sh
./start.sh
Windows:
start.cmd
Both scripts start the FastAPI proxy on http://localhost:5000 and forward all /mcp requests to Unreal’s MCP server at http://localhost:8000/mcp. You should see the following in the terminal:
Iniciando servidor HTTP local con Proxy CORS en el puerto 5000...
Abriendo el cliente web en el navegador (http://localhost:5000)...
To stop the server later, run stop.sh (macOS/Linux) or stop.cmd (Windows) from the same directory.
4

Open the web client

Your default browser opens automatically at http://localhost:5000. The SPA is divided into five panels:
PanelPurpose
ConnectionEnter the proxy URL (http://localhost:5000/mcp) and click Connect to initialize an MCP session
ToolsetsClick Fetch Tools to enumerate all registered toolsets and cache their schemas
Tool ExplorerBrowse discovered tools, read their descriptions, and inspect JSON input schemas
ExecuteSelect a tool, fill in arguments, and click Execute to send a JSON-RPC call
Response / StreamDisplays the raw SSE stream and the decoded JSON-RPC result in real time
5

Make your first tool call

  1. In the Connection panel, confirm the URL is http://localhost:5000/mcp and click Connect.
  2. In the Toolsets panel, click Fetch Tools. Wait a few seconds while the proxy enumerates and caches all toolset schemas.
  3. In the Tool Explorer, select list_toolsets from the tool list.
  4. Leave the arguments empty and click Execute.
The Response panel will display the raw SSE event followed by the parsed result — something like:
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "- ToolsetRegistry.AgentSkillToolset: Manages AI Agent Skills\n- editor_toolset.toolsets.scene.SceneTools: Scene management tools"
      }
    ]
  }
}
Each - Name: Description line is one registered toolset. You can now pass any of those names to describe_toolset to see every tool it exposes, or go straight to call_tool to invoke a specific action in the Unreal Editor.
If you don’t see toolsets beyond AgentSkillToolset, verify that EditorToolset, AutomationTestToolset, and SlateInspectorToolset are enabled in your .uproject and that the editor has been restarted since adding them. Also confirm that Auto Start Server is active under Edit → Editor Preferences → Model Context Protocol.

​
Next Steps

Web Client Overview

Deep-dive into the SPA’s panels, the SSE stream decoder, and the built-in Gemini multi-turn agent.

Plugin Setup

Step-by-step guide to enabling plugins, linking Build.cs dependencies, and creating your own custom toolsets.

Build docs developers (and LLMs) love

Get started for freeTalk to us