Documentation / User guides
Connect an AI agent (MCP)
Use Kismet as a Model Context Protocol (MCP) server for Unreal Engine. Let Claude Code, Codex, Cursor or any MCP client read, edit and compile Blueprints, materials and widgets in a running editor.
What the MCP server does
Kismet exposes its editor tools over the Model Context Protocol, so an external agent can read, edit and compile Blueprints, materials and widgets in a running Unreal Editor. The external agent brings its own model and its own loop; Kismet provides the tools, with the same validation and limits as its built-in panel. The server starts with the editor. There is nothing to install or enable beyond the plugin.
| Endpoint | http://127.0.0.1:8323/mcp (Streamable HTTP). If you set KISMETAI_PORT, use that port. |
|---|---|
| Authentication | Authorization: Bearer <token>, read from the mcp_token file in the .kismet folder of your home directory |
| Reach | This computer only. Requests from other machines and from web pages are refused. |
| Tools | Reading, writing, wiring and compiling Blueprints, asset search, source and log reading, plus the material, widget, project and discovery tools |
Get the access token
Every request needs a token. Kismet creates it the first time the endpoint receives a request and stores it in your home directory. The token belongs to the install, not the editor session, so a client you configure once keeps working after restarts.
- 1.
Open your project in Unreal Editor with Kismet enabled.
- 2.
Create the token by calling the endpoint once. The 401 reply is expected.
curl -s -o /dev/null -X POST http://127.0.0.1:8323/mcp - 3.
Read the token.
cat ~/.kismet/mcp_token
Connect a client
Any MCP client that supports Streamable HTTP and custom headers can connect. Point it at the endpoint and send the token as a bearer header.
- 1.
Claude Code
claude mcp add --transport http kismetai http://127.0.0.1:8323/mcp \ --header "Authorization: Bearer $(cat ~/.kismet/mcp_token)" - 2.
Other clients (Codex, Cursor and others)
Add a server with the URL http://127.0.0.1:8323/mcp and the header Authorization: Bearer followed by the token. The exact setting names differ between clients and versions, so follow your client’s own MCP instructions. Do not commit a project config file that contains the token.
- 3.
Check the connection by hand
curl -s http://127.0.0.1:8323/mcp \ -H "Authorization: Bearer $(cat ~/.kismet/mcp_token)" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Allow edits
The token lets a client call the tools, and reading works straight away. Changing assets needs an explicit grant from you, because nobody can approve an MCP call while it runs. Give the grant in the editor console, limited to the folder the agent may change.
- 1.
Allow edits and new assets under one folder.
KismetAI.Authority.Grant mcp edit,create /Game/Sandbox
Limits to know
| One call at a time | Tools run on the editor’s main thread. The editor is busy while a call runs, and a long compile blocks other calls. |
|---|---|
| No cancelling | A tool call runs to completion once it starts. |
| No streaming | Each reply is a single JSON response. |
| Panel diff view | Changes made over MCP are not shown in the Kismet panel’s diff view. |
- The client gets 401
- The token is missing or wrong. Read the mcp_token file again and update the client. If you deleted the file, a new token was written.
- The client cannot connect
- Unreal Editor must be running with Kismet enabled. Check the port: 8323 unless KISMETAI_PORT is set.
- Edits return AUTHORITY_REQUIRED
- Give the grant shown under Allow edits, for a folder that contains the asset.