The MCP Bridge panel

The bridge mod adds a panel to Dungeondraft under Settings → MCP Bridge. It shows whether your assistant is connected and what it last did, and holds the settings that are yours to choose. The panel appears once the mod is enabled and a map is open.

These settings belong to you. Your assistant can read them, so it knows how you want it to work, but no command it has can change them.

The top of the panel shows four lines:

• Listening on 127.0.0.1:port: the local port the bridge is answering on. The companion finds it on its own; you only need it when diagnosing a connection.
• Bridge protocol and build: the protocol version and a short fingerprint of the bridge that is actually running. It changes when a new bridge is loaded, so it tells you whether Dungeondraft picked up an update after a restart.
• Last request: the last thing your assistant asked for, and when. Connection checks are not counted. After you use the panel’s Undo button, this line says what was undone.
• Assistant history: how many of the assistant’s steps can be undone, out of 1,000.

Tick Pause AI edits to stop your assistant changing the map, for example while you edit by hand. While paused, anything that would change the map is refused, including your assistant’s own undo and redo. It can still read the map, take screenshots and export images, so it can see that you paused it and tell you. Untick the box to let it continue.

A pause lasts for this Dungeondraft session only. The next time you start Dungeondraft, the box is unticked again.

Undo the assistant’s last step reverses your assistant’s most recent edit, one step per click. A step is a whole tool call: a room built in one go, a batch of placed objects or a scatter undoes in one click.

This is the bridge’s own history, not Dungeondraft’s Ctrl+Z. It holds only edits made through the bridge, and Ctrl+Z does not reach them. The button works while AI edits are paused, but not while Dungeondraft is saving or exporting; the Last request line tells you if that, or anything else, stopped it.

Your assistant can redo a step you undid here, if you ask it to.

When Check for updates is ticked, the companion asks GitHub about once a day whether a newer battlemap-mcp release has been published, and your assistant tells you when one is. Only the release’s version number is read and nothing is downloaded. GitHub sees the request come from your IP address, but no version, identifier or map data is sent. If the check fails, for example offline, it stays silent. Untick the box to stop the check.

Placements decides where your assistant puts things when it was not told how to snap them:

• Place exactly where asked (the default): objects, walls and lights go at the exact coordinates your assistant chose.
• Snap to my grid: placements snap to the Custom Snap Mod’s grid, the same points your own cursor would land on. This applies only while snapping is on in Dungeondraft (the S key) and the Custom Snap Mod is enabled; otherwise nothing is moved, and your assistant is told why.

Detail scattered across an area stays loose either way, so rubble and leaves do not line up on grid points. If you ask your assistant for an exact position, or to snap something, that request wins over this setting.

The slider sets how many screenshots and exports are kept in the output folder, from 0 to 100; the default is 20. When a new one is saved, the oldest beyond that number are removed. At 0 nothing is kept: your assistant still sees each image, but there is no file left for you to open.

Verbose log writes a line to Dungeondraft’s log for each command the bridge runs. It is off by default and is meant for diagnosing a problem. Your assistant can turn it on or off too, when you are troubleshooting together, and the box follows.

Open output folder opens the folder where screenshots, exports and asset previews are saved, in your file manager. On Linux without a file manager, the panel shows the folder’s path instead.

If you run the companion download with BATTLEMAP_MCP_UPDATE_CHECK or BATTLEMAP_MCP_CAPTURE_RETENTION set, the variable wins over the panel for that setting. The panel still shows its own value, so check your environment if a change here seems to have no effect. The Claude desktop extension and the Claude Code plugin take no environment variables, so for them the panel is the only setting. See Local state for the full list.