> For the complete documentation index, see [llms.txt](https://adgit.gitbook.io/wickedengine-mcp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adgit.gitbook.io/wickedengine-mcp/welcome-to-wickedengine-mcp.md).

# Welcome to WickedEngine-MCP

This project integrates Large Language Model (LLM) tool-use capabilities into the [`Wicked Engine`](https://github.com/turanszkij/WickedEngine). It allows for natural language control over the engine's scene graph, scripting, and other functionalities by exposing engine features as tools that an LLM can call.

This integration utilizes both the [`humanus.cpp`](https://github.com/WHU-MYTH-Lab/humanus.cpp) and the [`cpp-mcp`](https://github.com/hkr04/cpp-mcp) libraries to create in-engine clients and MCP-compliant tool servers which can be optionally used with an external client, enabling communication between an LLM agent and the engine editor.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://adgit.gitbook.io/wickedengine-mcp/welcome-to-wickedengine-mcp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.