Mindomo

Create, update, clone or delete a theme — the single tool for theme authoring. Choose with 'op': • op=create-from-recipe — THE EASY PATH, use this by default. Provide 'recipe': describe the LOOK (palette, how many levels are filled, shape, connector) and the server builds the whole style tree. Returns the new id plus 'resolvedTheme' and a one-line 'summary'. • op=update-from-recipe — provide 'themeId' + 'recipe'; re-synthesizes that theme seeded from its CURRENT look, so a partial recipe acts as a patch (e.g. recipe={palette:{name:'ocean'}} recolours it and keeps its shapes, spacing and fonts). • op=create — provide 'theme' (a raw MapThemeJSON) when you need pixel-level control the recipe cannot express; returns the new theme id. • op=update — provide 'themeId' + 'theme'; FULL REPLACE of that theme (get_theme it first, modify, send back). Returns the id. • op=clone — provide 'themeId'; duplicates ANY theme (built-ins included) into your own editable copy and returns the new id. The fastest starting point when the user likes an existing look: clone it, then op=update the copy. • op=delete — provide 'themeId'. Only the user's own themes are editable (built-in gallery themes are read-only). Creating a theme does not apply it — call apply_theme, or pass recipe.applyToDiagramId to do both in one call. AUTHORING A THEME BY HAND (op=create/update). Only needed when op=create-from-recipe cannot express what you want — that op covers "vibrant colours, filled main topics, transparent rest" with {"palette":{"colors":[…]},"filledLevels":2}. If you do write the tree yourself: a theme is one canvas + one ALTERNATE-COLOUR palette + one style entry PER DEPTH. Three steps: (1) diagram.alternateColors.colors = the branch colour cycle (this is what "different colours per branch" means); diagram.fill.value = the canvas colour. (2) For every level you want FILLED with its branch colour, set that topics[i] style.fill.mode = "inherit-connection" — NOT "solid". "solid" paints every branch the same flat colour and the palette becomes invisible. Add border.mode "inherit-connection" + a width so the outline matches too. (3) For every level you want plain, set style.fill.mode = "transparent". HARD RULE: topics needs AT LEAST 3 entries — [0] root, [1] main topics, [2] level 2, whose style also covers every level deeper than the array. Indices 0/1/2 are read individually: omit one and that level falls back to a Mindomo default rather than to the level above. Do NOT set connector.stroke.color: that pins one line colour for the whole level and overrides the palette. Worked example — "vibrant alternate colours for the branches, filled main topics, transparent for the rest": {"op":"create","theme":{"type":"mindmap", "diagram":{"fill":{"value":"#fcfcfc","style":"solid"}, "alternateColors":{"mode":"palette","colors":["#ff6961","#ffb480","#f8f38d","#42d6a4","#08cad1","#59adf6","#9d94ff","#c780e8"], "lightText":"#ffffff","darkText":"#2d2d2d","lightnessFactor":0.6}}, "topics":[ {"style":{"shape":"capsule","fill":{"mode":"inherit-connection","pattern":"flat-border-dropshadow"},"border":{"mode":"inherit-connection","width":4},"font":{"size":25,"bold":true}}}, {"style":{"shape":"capsule","fill":{"mode":"inherit-connection","pattern":"flat-border"},"border":{"mode":"inherit-connection","width":2},"font":{"size":16}}}, {"style":{"shape":"line-bottom","fill":{"mode":"transparent"},"font":{"size":12,"color":"#2d2d2d"}}}], "summaryTopic":{"style":{"fill":{"mode":"inherit-connection"},"border":{"mode":"inherit-connection","width":2}}}}} If the user wants the level BELOW the main topics filled too, make topics[2] inherit-connection as well and append a transparent topics[3]. Creating a theme does not apply it — call apply_theme next.

edit_themes

Add, update, move, delete or restore topics in a diagram — the single tool for ALL topic edits. Choose the operation with 'op': • op=create — ADD topics (with optional nested subtopics). Provide 'branches'; each branch's parentId is optional (omit to add under the root/central topic). SUCCESS RESPONSE: {revision, branches} where 'branches' is the created topics as a TREE mirroring your request — each node is {id (the new shortId), title, subtopics[]}, all nesting levels, in request order. This IS the success result (a revision + the id tree = done); there is no separate {success:true} flag. Use these ids to anchor relations/boundaries/summaries — no follow-up read needed. Send the WHOLE map in ONE call (up to 1000 topics, nested subtopics count) — the server batches it internally, so prefer one big op=create over many small ones. New MAIN topics (added under the root) are auto-balanced across the left/right sides on a mindmap; set layout.orientation (mindmap-left/mindmap-right) on a branch to pick a side explicitly. op=create branches take the FULL Topic shape — title, description (topic notes), task (deadlines, priority, progress, duration, assignees, milestone), style, icons, links, layout, connector, collapsed, template — so a topic can be created WITH its deadline already set. This is the ONLY create path that carries task data (build_diagram does NOT), so a whole project map with tasks and deadlines is create_diagram {title, themeId} + this one call. • op=update — merge-patch existing topics (send only the fields to change). Provide 'topics', each with its id. Supports title, description, task {checkable (true = it IS a task — renders the checkbox), schedule {startDate, endDate — endDate is the DEADLINE / due date, yyyy-MM-dd}, priority(0-4; 0=highest), progressPercent(0-100), duration {value,unit}, isMilestone (a dated checkpoint), assignees (add/remove users by id, or virtual by uid)}, style {fill,border,font,shape,box}, connector {stroke,anchor,routing,markers,label} (the branch line), layout.orientation, collapsed, icons (emoji shortnames), links, media {url,path,type,size}, audio {url,path} (send media/audio with no url/path to clear it), and template (smart-template settings for TEMPLATE maps: placeholder/wiki/type, and fromTopicIds — existing child topics the server clones into the topic's insertable prototype branch; see edit_diagram_template / read_template_branches). layout.orientation on a topic restyles its subtree; on the ROOT topic it switches the whole map's layout (org-chart, timeline, fishbone, tree-*, concept, …). To REBALANCE a map (spread main topics evenly left/right), update the ROOT with layout.orientation="mindmap". NOTE: task.recurrence, task.occurrences, task.showCompleted, task.schedule.completedAt, task.completedBy, task.autoCalculate and task.color are applied on op=create ONLY — set them when creating the topic; sending them here has no effect. • op=move — reparent and/or reorder one topic. Provide 'topicId' (+ optional 'parentId', 'position', 'orientation'). Use orientation=mindmap-left/right to move a main topic to the other side. Re-mints the id; 'movedTopics' maps old→new. • op=delete — soft-delete topics (subtrees cascade). Provide 'ids' (topic shortIds). Returns a deleteCommandId. • op=restore — undo a delete. Provide 'ids' = the deleteCommandId(s) from op=delete. All ids are shortIds.

edit_topics

Export a diagram to a file. Provide the diagram GUID and a format; the file is returned as Base64 (contentBase64) with filename, mimeType and sizeBytes — decode contentBase64 to obtain the bytes. Plan tiers: FREE — txt, mom (Mindomo native); PREMIUM — pdf, png, svg, docx (Word), md (Markdown), opml, html, mm (FreeMind), mmap (MindManager); PROFESSIONAL — xls (Excel), pptx (PowerPoint). A format above the user's plan returns an upgrade message. Large exports are rejected — export those from the Mindomo app.

export_diagram

Get a diagram's metadata (name, dates, theme, type, creator, and link — a clickable URL that opens the diagram in the browser) by its id (GUID). This is ALSO the tool to SHOW a diagram: call it whenever the user asks to see / show / display / preview a map — hosts that support MCP widgets render the result as an inline interactive view of the map; otherwise present the link for the user to open. To support inline display, this tool may create or reuse the diagram's revocable AI viewer link in the user's Mindomo account.

get_diagram

Get a theme as JSON (its full MapThemeJSON definition) by id. Use to inspect a theme or to obtain a starting point: get a theme, modify the returned JSON, then edit_themes(op=update) it back. To start from a built-in instead, edit_themes(op=clone) is one call and loses nothing.

get_theme

List the diagrams the current user owns. Returns each diagram's id (GUID), name, modification date and link (a clickable URL that opens the diagram in the browser). Use the id with get_diagram / read_diagram / read_branches / open_diagram.

list_diagrams

List the themes available to the user: the built-in gallery plus the user's own. Each has id (GUID), layout (normal|concept|organigram|timeline|fishbone), builtin, and isDefault (the standard look for that layout). Themes are unnamed — to style a new map pick a built-in id for the target layout and pass it as themeId to build_diagram/create_diagram (or apply_theme later); inspect one with get_theme only if the exact colors matter.

list_themes

Read a topic and its subtree from a diagram. Omit topicId to read all root topics. depth 0 = just the topic (no children), N = N levels deep, -1 = the whole subtree. Ids are shortIds; topic user ids (assignees/completedBy/audit.createdBy) resolve to names via the 'users' list.

read_branches

Read a whole diagram: all topics (full tree), relations, boundaries and summaries, all with shortId ids. Use for a complete picture; read_branches for a single subtree. Topic user ids (assignees/completedBy/audit.createdBy/comment authors) resolve to names via the 'users' list. To support inline display, this tool may create or reuse the diagram's revocable AI viewer link in the user's Mindomo account.

read_diagram

Read a diagram's template-branch PROTOTYPE trees — the hidden insertable topics a smart-template topic offers (created with edit_topics via template.fromTopicIds). Each array element is a full Topic tree (same shape as read_branches topics, nested subtopics, ids are shortIds); join them to their owner topic via the owner's template.prototypeIds (from read_branches/read_diagram). Prototypes are NOT part of the normal topic tree — this is the only read that returns them. Optional topicId filters to one owner topic's prototypes.

read_template_branches

Rename a diagram and/or set its description. Provide the diagram GUID and a new name and/or description (both optional). Metadata change — no edit session needed; not covered by undo_change (rename again to revert). Setting a name also unlinks the diagram name from the root topic's title, as renaming in the Mindomo app does.

rename_diagram

Search across the diagrams the user can access. Use 'query' for the keyword search (matches all content — titles, notes, comments, links — like the dashboard). Optional structured filters to narrow: tasks (open|closed|all|due), priority (0-4), progress, assignedToId/assignedToName/assignedToEmail, createdById/createdByName/createdByEmail (topic creator), due/start/closed/created/modified (date windows), is (task|open|due), diagramsCreatedByMe, mapsCreatedById/mapsCreatedByName/mapsCreatedByEmail/mapsVisibility/mapsModified (diagram scope), limit. Returns matching diagrams (full GUID id) each with a link (a clickable URL that opens the diagram in the browser), its lightweight matching topics (shortId), a topicLinks map (topic shortId → clickable URL that opens that topic), and a users list resolving the user ids it references (createdBy, topic assignees/completedBy/audit.createdBy) to names.

search_diagrams

Search topics within one diagram. Use 'query' for the keyword search (matches all content like the dashboard); same structured filters as search_diagrams (diagramsCreatedByMe is ignored here). Returns the diagram id, its matching topics (shortId ids), a topicLinks map (topic shortId → clickable URL that opens that topic), and a users list resolving the topics' user ids (assignees/completedBy/audit.createdBy) to names.

search_topics

Revert a change previously made by THIS app on the diagram — either the change named by 'undoId' (returned by every write tool) or, when omitted, the app's most recent change. • To revert several changes, call once per change, NEWEST FIRST (undoIds in reverse order); undoing an older change while your own newer change still touches the same topics is refused as a conflict. • Only this app's changes qualify — a person's edits (or another app's) are never reverted; resolving without undoId skips right past them. • Covers topic create/delete/move, topic property updates, relations, boundaries, summaries, comments, and diagram style/theme/template changes. Value changes are revertible for 30 days (UNDO_EXPIRED after); a change whose previous value could not be captured answers UNDO_UNSUPPORTED. Reverting an op=restore is simply op=delete with the same topics; build_diagram's initial content is not a change and cannot be reverted. • If a later change by someone else touches the same topics, the revert is refused (UNDO_CONFLICT) rather than clobbering their work.

undo_change