Xmind MCP: Removing a Topic Also Removes Its Subtopics

Xmind’s October 29 announcement introduced Xmind Agent and connections that let outside AI assistants create, read and update mind maps. For an existing project map, one documented detail matters before asking an assistant to tidy its structure: removing a topic also removes its subtopics.

Xmind’s company-issued October 29 announcement

Look below the heading before removing it

Xmind’s official MCP guide says to identify the map, sheet and topics to change. It explicitly warns that deleting a topic removes its children. It also says MCP edits are saved to the same map. A branch title that looks obsolete can therefore contain work that still matters.

Xmind’s MCP guide: editing topics and restoring versions

Consider this fictional planning exercise, not a test of Xmind. A team has a map called Autumn Workshop, with two sheets: Event Plan and Supplier Research. On Event Plan, a branch named Old Venue contains three children: Room capacity notes, Deposit question and Accessibility checklist. The team has chosen a different venue, but two of those notes remain useful.

An instruction to remove Old Venue would target the parent. It would not express the team’s real intention to keep the unresolved deposit question and the accessibility checklist. The problem starts with the requested scope, before the assistant chooses any tool.

Write the intended destination for useful children

First inspect the branch’s contents. In the exercise, decide which notes are historical and which belong in the active plan. Then describe the desired result explicitly: in Autumn Workshop’s Event Plan sheet, move Deposit question to Open Questions and Accessibility checklist to New Venue; preserve their notes; remove the remaining Old Venue branch only after checking the moves.

That is a proposed editing method, not a guarantee that a client will execute several operations as one transaction. For a first trial, use a disposable map with invented information. Check each result before requesting the next change if the assistant or client does not make the sequence clear.

Afterward, open the current map and inspect both destination branches. Confirm the useful children and their notes remain, the intended old branch is gone, and Supplier Research is unchanged. Record any difference from the requested result before continuing.

Check how long recovery remains available

Xmind’s help page limits this recovery guidance to online maps in My Works or Team Space. It lists a three-day version-history window for Free and Pro, and 30 days for Premium and Business. These are the published plan distinctions when checked; confirm the current terms for your account.

Xmind Help: online-file recovery and plan windows

The documented route is to open the map on the web, choose File > Version History from the main menu, select the version and restore it. The MCP guide says to ask the assistant to read the map again after a restoration. Its earlier conversation may describe a state you have now replaced.

In the fictional exercise, do not assume the three-day window will cover a review scheduled a week later. Arrange the review while recovery is available, or choose another preservation method that your team has checked. The help page does not establish an unlimited archive or the recovery behavior of every local file.

Confirm access and plan limits separately

Xmind’s MCP product page says the server has no separate usage fee, while account storage and premium-feature limits still apply. Connection availability alone does not establish that a particular account can perform every planned edit.

Xmind MCP: supported operations and account limits

A useful cleanup request names the file and sheet, identifies the exact parent and children, and says where retained work should go. Review the resulting map while the relevant recovery window is open. This keeps the editing decision tied to the information your team intends to preserve.