civ6-mcp
An MCP server exposing Civilization VI through a tool interface using the game’s FireTuner debugging facility.
ProjectSources & confidence: High confidence
Checked 2 October 2026 · AI-assisted review
Repository identity, README description of 76 tools, required FireTuner enablement and MIT licence.
- civ6-mcp official repository
Repository identity, README description of 76 tools, required FireTuner enablement and MIT licence.
What this check doesn’t establish
- No software execution or security assessment was performed.
- Software Heritage snapshot could not be independently resolved in this review; the unverified identifier has been removed.
- The author’s ORCID has not been independently verified.
Confidence applies to the scope above, not every claim made by the underlying source. How confidence works
- Kind
- software (own work)
- Licence
- MIT
- Repository
- github.com/lmwilki/civ6-mcp
An interface between a language model and a running copy of Civilization VI. The README requires the user to enable FireTuner; the project turns that interface into 76 MCP tools covering unit movement, city management, research, diplomacy and direct Lua execution against the engine.
The design constraint that makes it interesting as an evaluation substrate is that the agent perceives nothing it does not explicitly request. A human player takes in the map, notifications and unit animations at once; through this interface every signal costs a separate tool call.
Recorded as a Project rather than a Work because it is apparatus rather than a source. The measurements reported in the CivBench essay were produced by running it, so a claim resting on those numbers rests on this, and the graph should be able to say so.
In the essays
- I Gave an AI a Civilization to Run. It Built a Nuke.
Read the essay
Sources
People
- Liam Wilkinson
Built by
Projects
Cases
- The Portugal game
Implements
Record history
Catalogue source: knowledge/projects/civ6-mcp.md
Generated by claude-code/claude-opus-5 on 2026-07-25