xmind_add_boundary
ChatGPTAdd boundaries to a mindmap. rangeType 'parent' wraps the whole topic; 'children' groups a contiguous range of the topic's attached children (0-based rangeStart..rangeEnd inclusive). The topic is identified by the id in its <!--t:id--> anchor. An optional title labels the boundary — use it to give a run of siblings a collective name ("MVP scope") or a status tag ("done" / "TBD"); omit it for a pure visual highlight. Put every boundary you are adding in one call via items (up to 200) — do NOT call this once per boundary. An item with bad arguments is skipped and reported; the rest are still written.
xmind_add_relationship
ChatGPTAdd relationships (association lines) between pairs of endpoints. Each endpoint is usually a topic (id from its <!--t:id--> anchor) but may also be a boundary (<!--b:id-->). Both endpoints must already exist; an optional title labels the line. For a multi-sheet file, pass the sheetId the endpoints belong to (from xmind_list_sheets); omit it for the first sheet. Put every line you are drawing in one call via items (up to 200) — do NOT call this once per line. An item with bad arguments is skipped and reported; the rest are still written.
xmind_add_sheet
ChatGPTAdd a new sheet (a new map) to an existing mindmap file. Pass markdown and design exactly as xmind_create_mindmap takes them and the map is built in this one call — marks, notes and style included; load the guide for the kind of map first with xmind_get_mindmap_guide. Without markdown the sheet starts as a single styled root topic, to fill in with xmind_edit_mindmap. Returns the new sheet id — pass it straight to xmind_edit_mindmap as sheetId. No xmind_list_sheets call is needed.
xmind_add_summary
ChatGPTAdd summaries over contiguous ranges of a topic's children (a bracket grouping children [rangeStart..rangeEnd] inclusive, with an optional summary note). topicId is the parent topic (from its <!--t:id--> anchor); rangeStart/rangeEnd are zero-based child indices. Put every summary you are adding in one call via items (up to 200) — do NOT call this once per summary. An item with bad arguments is skipped and reported; the rest are still written.
xmind_add_topic_link
ChatGPTLink one topic to another topic in the same map (an internal cross-reference / jump). Clicking the source topic navigates to the target. Both ids come from <!--t:id--> anchors. A topic can hold one link, so this replaces any existing hyperlink on the source topic.
xmind_clear_task
ChatGPTRemove all task data (todo state and any scheduled/gantt fields) from topics, by their <!--t:id--> anchors. Use this to turn tasks back into plain topics. Pass every topic you want to clear in one call — topicIds accepts up to 200 and they are cleared together, so do NOT call this once per topic.
xmind_create_folder
ChatGPTCreate a folder in the drive. Pass folderId to create it inside an existing folder or space; omit it to create at the root of the default space. The destination must be in the team this connection is authorized for. Returns the new folderId — pass it to xmind_create_mindmap or xmind_move_file to put files in it.
xmind_create_mindmap
ChatGPTUse this when the user wants to create a mind map, visualize hierarchical ideas, or generate a Xmind file. Do not use for flowcharts, tables, or linear content.
xmind_edit_mindmap
ChatGPTUpdate an existing mindmap with new markdown content. Read the mindmap first with xmind_read_mindmap, make your changes to the markdown, then write back the full updated content. The visual theme and layout settings are preserved.
xmind_get_mindmap_guide
ChatGPTLoad the authoring guide for one kind of map BEFORE building it with xmind_create_mindmap or xmind_add_sheet — how that kind of content is cut, which design it takes, and a worked example of the markdown and its marks. Pick by what the user asked for: - mindmap-general: Use this when no other scenario fits better: laying out knowledge, explaining a concept, notes on a book or a course, making an argument, brainstorming, a goal tree (OKR), todos and schedules — structuring any subject at all. - mindmap-travel: Laying a trip out as a map you can actually follow: how the days go, where to stay and how to get around, a destination guide, a multi-city or driving route, a packing and booking list. - mindmap-swot: SWOT, competitive assessment, strategic review: setting a subject’s internal strengths and weaknesses beside its external opportunities and threats, to see where it stands and what follows. - mindmap-comparison-decision: Comparing and choosing between options: A vs B, tool selection, purchasing, vendor evaluation, weighing approaches, and "should we do this at all". Not a neutral introduction to a subject. - mindmap-process-playbook: Turning something done repeatedly, and handed to other people to follow, into a procedure they can execute: an SOP, an operating manual, incident handling, approvals and handovers, onboarding, a checklist. - mindmap-timeline-narrative: Explaining in time how something that has already happened came to be: a life, how a company or product evolved, a technical history, a stretch of history, how an incident unfolded. If shuffling the periods breaks the meaning, this is it. - mindmap-meeting-notes: Laying out what a meeting produced: what was decided, who is doing what, and what is still open. Minutes, a weekly sync, a retrospective and a pre-meeting agenda all belong here. Nothing fits → mindmap-general. Pass the same scenario on as design.scenario.
xmind_get_topic
ChatGPTGet the full rich content of one topic by its id, plus its direct children's ids and titles. Returns the note (plain text in note, rich HTML in noteHtml), markers, labels, hyperlink, image and task — the values the read markdown only flags the presence of (a finished task's done is the one value it carries). Task comes back in task (null when the topic has none): status is the xmind_set_todo checkbox, progress / start / due / duration / priority the xmind_set_planned_task schedule, in the same units those tools take. When isRolledUp is true those values are aggregated from the scheduled descendants rather than set on this topic — report them, but do not write them back or you copy the children's schedule onto the parent. Call it on a child id to walk one level deeper. That is cheaper than xmind_read_mindmap when you want one branch of a large map, but NOT when a node has hundreds of children — check childCount first, and read the whole map instead if this node holds most of it. Start from the rootTopicId that xmind_list_sheets returns. Floating topics come back in detachedChildren with their rich content; xmind_read_mindmap names them in its overview too, but only by id and title. Each list is capped at 200: childCount / detachedChildCount carry the true totals, and childrenTruncated / detachedChildrenTruncated say which was cut. There is no cursor. A cut children list can be read in full with xmind_read_mindmap when this topic is part of the outline; a floating topic's own children never appear there, so keep drilling with this tool.
xmind_list_folders
ChatGPTList the direct child folders of a folder or space, plus breadcrumbs back to the space root. Pass a spaceId from xmind_list_spaces or a folderId from a previous call as folderId (a space's root folder id IS its spaceId); omit it for the default space's root. Returns one level only — call again with a child's folderId to go deeper. When the response includes nextCursor, pass it back as cursor (with the same folderId) to fetch more folders at this level.
xmind_list_mindmaps
ChatGPTList mindmap files in the current team workspace that the user has recently opened, sorted by most recently opened. Returns file IDs, names, and last-opened times. Use this to find a mindmap before reading or editing it.
xmind_list_resources
ChatGPTList everything a mindmap file references: attachments, topic images, audio notes, web links and local-file links. Each entry names the topic that carries it, so you can pass topicId to xmind_get_topic to see it in context. Returns the whole file unless you pass sheetId. This lists references, not bytes — use it to answer "what is in this file" without reading the map. Returns at most 100 entries by default; total always carries the true count and truncated says whether the list was cut. When it is cut, either raise limit (up to 500) or narrow with sheetId — do not assume what came back is everything.
xmind_list_sheets
ChatGPTList all sheets (maps) in a mindmap file, each with its id, title, root topic id and topic count. A file can hold several sheets; pass a sheet's id value as the sheetId argument to xmind_read_mindmap / xmind_edit_mindmap to work on that sheet.
xmind_list_spaces
ChatGPTList the spaces (top-level areas) of the current team that the user has access to. Each space's id doubles as its root folder id — pass a spaceId as folderId to xmind_list_folders, xmind_list_mindmaps, or xmind_create_mindmap. The entry marked isDefault is where mindmaps go when folderId is omitted. Typical flow: xmind_list_spaces → xmind_list_folders → xmind_create_folder / xmind_create_mindmap / xmind_move_file.
xmind_list_teammates
ChatGPTList the members of the team this connection is authorized for, with their xmindId and display name. Use it to turn a person's name into the xmindId that other tools address them by. Read-only: it cannot invite, remove, or change anyone's role. A name may come back empty if the account service is slow — match on xmindId in that case.
xmind_move_file
ChatGPTMove one or more mindmap files into a folder or space. Pass every file you want moved in a single call — moving them one at a time burns the per-user rate limit. Access is checked for every file before any is moved, so an unreachable file rejects the whole call without moving anything. Source files and destination must both be in the team this connection is authorized for; a file from another team cannot be moved here. Files already in the destination come back under alreadyInPlace, not movedFileIds.
xmind_read_mindmap
ChatGPTRead an existing mindmap and return its content as markdown. Use this to see the current structure before making edits.
xmind_remove_annotation
ChatGPTRemove an annotation — a relationship, boundary or summary — by its id (the value inside its <!--r:id-->, <!--b:id--> or <!--s:id--> anchor in the xmind_read_mindmap overview). Annotations are the layer attached to topics; removing one never deletes a topic. To remove a topic, use xmind_remove_topic. To restructure the map, use xmind_edit_mindmap.
xmind_remove_topic
ChatGPTRemove a single topic (and its whole subtree) by its id (from the <!--t:id--> anchor in xmind_read_mindmap output). Use this when you want to delete one known topic. Because deleting a topic also deletes every descendant, a topic that has children requires confirm:true — calling without it returns the descendant count so you can confirm the impact first. To make many structural changes at once (add/move/delete several topics, change the hierarchy), use xmind_edit_mindmap instead.
xmind_rename_file
ChatGPTRename an existing file, replacing its current name. The file must be in the team this connection is authorized for.
xmind_rename_folder
ChatGPTRename an existing folder, replacing its current name. Space roots cannot be renamed. The folder must be in the authorized team.
xmind_restore_file
ChatGPTRestore a file from the trash to the active drive. The file must be in the authorized team, and restoring it must fit the current plan’s mind map limit.
xmind_set_color_theme
ChatGPTChange a sheet's color palette. ALWAYS whole-sheet — color themes can't be scoped to a branch (there's no per-topic colorThemeId). To emphasize individual topics, use xmind_set_topic_style instead (per-topic overrides sit on top of the theme and survive a theme switch). Hue-continuity rule: when the user asks for a relative tweak (lighter / darker / softer / more vibrant), stay within the SAME hue family — use the hex swatches below to pick the nearest neighbor. Switch hue family only when the user names a different color or vibe. Dawn is the default. Greens & Teals: - Rainforest — bg #ffffff + #9ceaef #68d8d6 #06AFA9 — bright tropical teal-green - RainforestDark — bg #046562 + #c4fff9 #9ceaef #68d8d6 #06AFA9 — the same tropical teals on a deep teal ground - Woodland — bg #F9FFEB + #E1C356 #5B805C #86964F #B3C785 — muted forest green with ochre accent - WoodlandDark — bg #1F2513 + #E1C356 #5B805C #86964F #B3C785 — the same forest palette on near-black bark - GreenTea — bg #1F2B1D + #b6ad90 #579360 #656d4a #265834 — deep olive / dark forest, calm - Vanilla — bg #FFFFFF + #30E3CA #11999E #40514E — cool teal-mint - VanillaDark — bg #0D4040 + #E4F9F5 #30E3CA #11999E #40514E — mint on a deep pine ground - Quaint — bg #F9F5DE + #4B9D9D #7884A4 #AA79AA — parchment ground, muted teal / slate / mauve - QuaintDark — bg #153E5D + #DFDDCE #4B9D9D #7884A4 #AA79AA — the same muted trio on petrol blue Blues: - Constancy — bg #ffffff + #3949AB #00897B #EEEEEE — white ground, indigo centre with a teal accent, businesslike - Hawaii — bg #FFFFFF + #B7D6E8 #4A94C3 #4B9383 #D29F55 — beach blue + sand accent - Space — bg #0D2F42 + #81c3d7 #3a7ca5 #2f6690 #16425b — deep navy, premium dark - DeepSea — bg #000D2D + #6EE2FD #3BB6E3 #135CAE — very dark underwater navy + cyan - CyberPunk — bg #ffffff + #72efdd #56cfe1 #4ea8de #5e60ce — neon teal through indigo, electric - Forid — bg #EDF3FF + #FFAA39 #D389D5 #1692D2 — pale blue paper, amber / orchid / azure - ForidDark — bg #0A052E + #C1E554 #FFAA39 #D389D5 #1692D2 — the same trio glowing on midnight indigo - Variety — bg #F6F5F5 + #FFC947 #E46D57 #1F3C88 — off-white ground, amber / coral / navy - VarietyDark — bg #070D59 + #9BFFED #FFC947 #E46D57 #1F3C88 — the same on deep navy, with a mint highlight - Pinecone — bg #1D414B + #64625C #978477 #AA9FA3 #D1BFAF — slate teal ground, warm greys and taupe Purples & Pinks: - Sakura — bg #FFE3E8 + #FFB4B6 #D1C3BD #C1CFDE — pale cherry blossom, very light - Roses — bg #fff0f3 + #ffb3c1 #ff758f #c9184a — warm dusty pink, medium intensity - Cream — bg #ffe0e5 + #ffebee #2196F3 — blush ground with a single blue pop - Dazzling — bg #FFFFFF + #EFD7E6 #FF7DC1 #A239EA #5C37E5 — white ground, hot pink → violet - DazzlingDark — bg #092933 + #EFD7E6 #FF7DC1 #A239EA #5C37E5 — the same neons on near-black teal - Innocence — bg #FDF8E7 + #FDC9D1 #EA618A #A4D0F9 #4F73BA — cream ground, candy pink and cornflower - Violet — bg #FFFBEF + #FBD58A #DCBEF4 #b67be6 #9d4edd — ivory ground, amber with orchid and violet - Freshness — bg #f0f0f0 + #F2BDC7 #5BA683 #B796D9 — light grey ground, pastel rose / jade / lilac Reds / Warm / Earth: - Fire — bg #FFFFFF + #FDD29A #F9A655 #FC901A #E04B51 #A4564C — red-orange flame, energetic - Dancing — bg #FFFFFF + #4E60EF #EB4758 #AA0E1D — blue + crimson contrast, dynamic - DancingDark — bg #363026 + #4E60EF #EB4758 #FFF8E0 #AA0E1D — the same contrast on dark umber - Sophisticated — bg #FDFBF7 + #7D5A2C #DFCAA4 #C49C64 #D3381D — refined brown with a crimson accent - SophisticatedDark — bg #1E1D1A + #7D5A2C #DFCAA4 #C49C64 #D3381D — the same browns on near-black - Vintage — bg #264653 + #F4A261 #DC856F #A4705E #2A9D8F — dark teal + retro warm - Dessert — bg #F9F8ED + #FFBC9F #D8AC8F #83c5be — warm sand + teal accent - DessertDark — bg #006d77 + #FFEDD2 #FFBC9F #D8AC8F #83c5be — the same sands on a teal ground - Kimono — bg #FFFFFF + #FFABAA #FF7B31 #8CB5FF #4A51D9 — vibrant Japanese textile mix - KimonoDark — bg #191959 + #FFABAA #FF7B31 #8CB5FF #4A51D9 — the same text…
xmind_set_planned_task
ChatGPTSet scheduled / gantt task fields on topics: start and due dates (epoch ms), duration (ms), progress (0..1) and priority (0..9). Overwrites supplied fields in existing task data; omitted fields are preserved. Each item carries its own schedule, so put every topic you are scheduling in one call (up to 200 items) — do NOT call this once per topic; a project plan is one call, not one per row. Each item must set at least one field. This is a paid feature — it requires the file's plan to allow gantt editing.
xmind_set_structure
ChatGPTSet the layout (structure) of a mindmap. Scope: - Whole-sheet (omit topicId): the sheet's root adopts this structure, re-laying out the entire map. - Branch-scoped (pass topicId of a non-root topic): only that topic's subtree uses the structure; siblings and the rest of the sheet are untouched. Structures: - MindMap — general brainstorming; the default radial layout, fits most topics - MindMapUnbalanced — radial map where branches sit on whichever side balances the tree - LogicChartRight — left-to-right outlines, argument chains, document structure - LogicChartLeft — right-to-left logic chart (RTL reading or mirrored layout) - BraceMapRight — part-whole breakdowns shown with braces, left-to-right - BraceMapLeft — part-whole breakdowns shown with braces, right-to-left - OrgChartDown — top-down reporting lines, taxonomies, hierarchies with multiple branches - OrgChartUp — bottom-up org chart (roots-up hierarchy) - TreeChartRight — single-trunk hierarchical classification, left-to-right (e.g. taxonomy, directory) - TreeChartLeft — single-trunk hierarchical classification, right-to-left - TreeChartBalanced — balanced tree chart that splits children to both sides of a vertical trunk - TreeChartBranchAlignedLeft — tree chart with branch-aligned children, left-to-right - TreeChartBranchAlignedRight — tree chart with branch-aligned children, right-to-left - TimelineHorizontal — chronological events, roadmaps, milestones along a horizontal axis - TimelineVertical — chronological events down a vertical axis - TimelineHorizontalOffAxis — horizontal timeline with events alternating above/below the axis - FishboneRight — cause-and-effect / Ishikawa root-cause analysis, head on the right - FishboneLeft — cause-and-effect / Ishikawa root-cause analysis, head on the left - TreeTable — hierarchical data viewed as a nested table, title column on the left - TreeTableTopTitle — hierarchical data as a nested table, title row on top - MatrixRow — 2D comparison grid laid out row-first (e.g. feature matrix, pros/cons) - MatrixColumn — 2D comparison grid laid out column-first
xmind_set_todo
ChatGPTMark topics as todos and set their checkbox state to 'todo' or 'done' (ids come from each topic's <!--t:id--> anchor). Pass every topic you want to set in one call — topicIds accepts up to 200 and they are applied together, so do NOT call this once per topic. One call sets one status; to mix states, make one call per status. This is the basic task checkbox; for scheduled/gantt fields (start, due, duration, progress) use xmind_set_planned_task. Attach a checkbox only where the topic is something to DO — an action item, a checklist entry, a next step. A checklist-style map (a weekly plan, a launch checklist) carries one on almost every leaf; a knowledge or explanation map, whose leaves are facts, carries none.
xmind_set_topic_attrs
ChatGPTSet attributes on topics by id (from the <!--t:id--> anchor in xmind_read_mindmap output). Supports note, hyperlink (href), labels and markers. Supplied attributes replace their existing values; omitted attributes are preserved. Each item carries its own values, so put every topic you want to edit in one call (up to 200 items) — do NOT call this once per topic. Other topic properties cannot be changed through this tool. A note supplements what the topic title cannot hold — a figure, a source, an example, an exception. A note that restates its topic means the topic is what needs fixing, and a map should still read without opening any note. Attach a marker only where the content carries that semantics (a priority, a status, a rating, an alert); markers scattered as decoration make a map noisier, not clearer. The ids themselves are listed on the markers field — an id outside that set is written through as-is, so take one from there or from a topic you have read rather than composing one.
xmind_set_topic_image
ChatGPTAttach images to topics by id (from the <!--t:id--> anchor in xmind_read_mindmap output). Provide a public http(s) image URL per item; the server fetches and stores it. Supports png, jpg, webp, gif, svg and bmp. Each image is displayed at a size the editor computes automatically. Put every image you are attaching in one call via items (up to 20 — lower than the other batch tools because each one is fetched over the network). An item that cannot be fetched or whose topic is missing is skipped and reported; the rest are still attached.
xmind_set_topic_style
ChatGPTSet per-topic style overrides on topics by id (from each <!--t:id--> anchor): fill/text/line/border color, bold, italic, strike-through, and font size. The style you pass is applied to EVERY topic in topicIds, so put all topics that should share a look in one call (up to 200) — do NOT call this once per topic; use separate calls only for genuinely different styles. These overrides sit ON TOP of the sheet color theme — the topic renders with the override while its siblings keep the theme default, and the override survives a later theme switch. Use this to emphasize specific topics; to recolor the whole map use xmind_set_color_theme instead. For each field, pass a value to set it or null to clear that override (fall back to the theme). Colors are 6-digit hex (#RRGGBB). Use bold for emphasis — do NOT bump fontSize as an emphasis proxy.
xmind_show_mindmap
ChatGPTShow a mindmap to the user: renders the map where the client can display one, and hands back a link where it cannot. Nothing else puts a map in front of the user: xmind_create_mindmap and xmind_edit_mindmap write the file and display nothing. So call this once, after every change is done, whenever the user should see the result — a map they cannot see is a map they will ask for again. It returns nothing for you to reason about; read the content with xmind_read_mindmap instead.
xmind_trash_file
ChatGPTMove a file to the trash, removing it from the active drive and recent files. This is reversible with xmind_restore_file; it does not permanently delete the file. The file must be in the authorized team.
xmind_update_relationship
ChatGPTUpdate an existing relationship by its id (the value inside its <!--r:id--> anchor in the xmind_read_mindmap overview). Can change the title and/or re-point its source / target to another element (usually a topic, but a boundary id is also valid). Provide at least one of title, sourceId, targetId.
xmind_whoami
ChatGPTReport which Xmind team this connection is authorized for, and which other teams the user belongs to. A connection reaches exactly one team: every other tool here — listing, reading, editing — is confined to it, and a file in another team is refused however the file id was obtained. Call this before acting on a file id the user supplied, so you can say which team you can reach instead of discovering the boundary by failing. Reaching a team in otherTeams needs the user to re-authorize Xmind for it, and to accept the invitation first if theirs is still pending.
