miMind AI

The AI assistant built into your mind maps

Generate complete maps from a sentence, chat with the map you have open, and let AI suggest what comes next — on every platform miMind runs on.

Generate a Map

From the map list AI button

Tap the round pulsing AI button in your map list to create a brand-new map. Describe what you want, optionally pick a layout, theme and level of detail, attach files, images or links — then hit Generate and watch the map build itself node by node.

By default the map is built from concise node titles. Turn on Generate Node Notes if you also want the AI to write longer explanatory notes on the nodes.

Turn on Generate Background Scene and the map arrives with a scene background made for it: a gentle scene that suits what the map is about, in colours that sit well with its theme, designed while the map builds and saved with it. The scene also goes into Yours among your scene cards. If it can’t be made, the map opens without one and a notice says so. The switch is off until you turn it on, and miMind remembers your choice on this device. Needs a miMind AI subscription (without one the switch shows a lock); it is not part of the one-time trial.

Leave the layout on Auto and the AI picks one to suit the material: a dated timeline for histories, biographies and anything that happened on dates — each event placed on a real axis by its own date — or an Orbital Station when the main branches are all the same kind of thing (all planets, all programming languages). Everything else gets the standard tree. Choose a layout yourself and the AI uses that one instead, including any of the advanced layouts.

From a topic or description

A study plan for learning Spanish in 6 months, with weekly goals Business plan for a small coffee roastery — products, marketing, finances, suppliers

From pasted text

Paste meeting notes, an article, or any longer text — the AI organizes it into a structured map.

Turn these meeting notes into an action map: [paste your notes]

From a URL

Paste a link — the AI reads the page and maps its content.

https://en.wikipedia.org/wiki/Solar_System — map the main facts

With attachments

Use the + Add Files / Images button to attach material for the AI to build the map from. What you can attach:

  • PDFs — read page by page, including layout and tables. Up to 2 per request, 8 MB each.
  • Images (PNG, JPEG, GIF, WebP) — analyzed with vision. Up to 4 per request.
  • Text and code files — .txt, .md, .csv, .json, source files and similar; the first ~50 KB of each is read.
  • Links — the page is fetched and mapped alongside everything else.

Attach several files at once and the AI gives each distinct component its own root node, so you get side-by-side maps in one document rather than one crowded tree.

Video, archives, Word and Excel files can’t be read — those are refused with a note naming the file, so nothing is ever silently left out of your map.

Map the key findings, method and limitations of this paper [attach PDF] Turn this scanned handout into a revision map [attach PDF] Map the architecture these files describe — one root per module [attach several source files] Structure this whiteboard photo into a proper map [attach image] Build a map comparing these two product sheets [attach 2 PDFs]

Chat with Your Map

The in-editor AI panel AI button

Inside any open map, tap the AI button (above the zoom controls) to open the chat panel. The assistant sees your map's structure and your selected node, so you can talk about it directly. On phones the panel is a compact bottom sheet — swipe down or tap the top arrow to dismiss it.

  • Direct commands act on the map — added nodes and edits are applied immediately and can always be undone.
  • Suggestions are propose-then-accept — the idea button (or asking for ideas) shows ghost nodes you can keep or drop, and reply options appear as tappable chips (select several, then confirm with the checkmark).
  • Animate connections Premium — ask to animate the link between two nodes and the assistant offers a few live animated previews right in the chat; tap one to apply it, or tap Other to describe exactly what you want (effects, an emoji to send along the line, direction and speed).
  • Scene backgrounds Premium — ask for a background and the assistant puts a matching scene behind your map, with buttons to keep it or try another (see Scene Backgrounds).
  • Attachments — the + button adds PDFs, images, text files and links to the conversation (see below).
  • Conversations — each map keeps its recent conversations; switch or start new ones from the title dropdown.

Working with attachments in chat

Attach with the + button, then say what to do with it. The assistant reads the attachment and edits your map from it — the same file types as map generation: PDFs (up to 2, 8 MB each), images, text and code files, and links.

Attachments stay available for follow-up questions. Attach a PDF once and you can keep asking about it for the rest of the conversation — including after closing and reopening the map — without attaching it again.

Build from a document

Add the key points of this PDF under “Research” [attach PDF] Now expand section 3 into its own branch What does the PDF say about cost? Add it as notes on the selected node

Compare against the map

Compare this spec to my map and add whatever’s missing [attach file] Which requirements in this document aren’t covered by the map yet?

From an image

What is in this screenshot? Map it. [attach image] Turn this diagram into nodes under the selected node [attach image]

If a file can’t be read (video, archive, Word or Excel), the panel says so straight away rather than letting you send a message about a document the assistant never received.

Command Reference — things to ask

Building & expanding

Add branches / nodes

Add a branch about competitor analysis with 5 sub-points Add three pros and three cons under the selected node

Expand with suggestions (ghost nodes)

Suggest ways to expand this map What am I missing under “Marketing”?

Enriching nodes

Notes & summaries

In chat the AI keeps nodes to short titles and adds notes only when you ask — request a description, summary, or details (or tell it to always add notes).

Write a short note on the selected node explaining the concept Summarize this whole branch into one note on its root From now on, always add a short note to every node you create

Links, tables, lists & tasks

Add a comparison table of the three options under “Vendors” Turn these nodes into a task checklist Add useful links about each framework

Pictures

Ask for images and you get the actual pictures placed on the nodes, not links to them. The assistant describes what each node should show and miMind looks the pictures up for you, so adding a dozen at once is quick.

Ask for an icon or a logo instead and you get line art on a transparent background, which sits cleanly on a coloured node. New maps get one of these on the central node automatically — a single image that sums up what the map is about.

Add a picture to each of the landmark nodes Put an image of the Eiffel Tower on the selected node Give the main node an icon for this topic

Videos

Ask for a video and the assistant attaches a player to the node. Every video is checked before it lands, so dead or private links don't end up on your map.

Add a good intro video to the selected node

Icons, emoji & visuals

Add fitting emoji to the top-level branches

Restructuring & understanding

Undoing what the AI did

Every reply that changed your map carries an Undo this change button, which reverses that whole turn in one press — however many nodes, pictures and edits it involved. You can also just type undo (or redo) in the chat box; those are handled instantly on your device and don't use any of your AI allowance.

undo redo

Update & retitle

Rename the selected node to something clearer Rewrite the titles in this branch to be shorter

Ask about the map

What does this map say about the timeline? Which branch needs the most work?

Work with attachments

Add the key points of this PDF under “Research” [attach PDF] Now expand section 3 — no need to attach the PDF again Compare this spec to my map and add what’s missing [attach file] What is in this screenshot? Map it. [attach image]

Scene Backgrounds

A gentle scene behind your map Premium

Tap a node's Style button (the gear), open Theme, and under Canvas turn on Scene background to put a soft vector scene behind the whole map: aurora curtains, a slow drift through stars, sun rays under water, forests, mountains, the sea, rivers and lakes, the seasons, gentle abstract shapes. 64 scenes are built in, in ten groups — Sky & space, Clouds & weather, Wind & Wave, Forest & woods, Seasons, Ocean & beach, Rivers & water, Under the sea, Mountains & desert, and Abstract & calm. Most move, slowly — many in depth, their nearer layers a little faster than the farther ones, so ranges, tree lines and cloud banks drift past at different speeds; some are still pictures.

  • Animate — turn it off to hold a moving scene still. Exports and thumbnails always show the still frame.
  • Strength — how far the scene stands out from the canvas colour.
  • Speed — how fast a moving scene moves.
  • 3D depth — how far the scene's layers follow you as you pan and zoom the map, the nearer ones more than the farther ones; at 0 the scene stays put. Exports always show it at rest.

Scenes are made to stay behind your work: slow and sparse, quieter in the middle of the screen, with colours that follow the map's theme. On a dark theme they are expressive; on a light one they paint as daylight — a sky, hills, trees and water in their own colours, easing off behind the map. Northern Lights and the Wind & Wave silks go further on dark themes: they fill the sky with vivid colour. A scene takes the place of the gradient background (the two don't combine), is saved with the map, and can be undone like any other style change.

Scene backgrounds are a subscription feature, so the Scene background switch carries a Premium tag. Every miMind subscription includes them — Premium, Business and miMind AI — but one-time purchases and older licences don’t. Without a subscription you can still try any scene in the style sheet, built-in or your own: it is taken back when you close the sheet or tap outside it, and miMind tells you why (in the Map Builder, Finish does the same). A scene that comes with a map stays: a map shared with you, or made by an agent over MCP, shows its scene whatever your plan.

Generate with AI miMind AI

Above the scene cards, Generate with AI designs a new scene from your description. Describe the background you want, choose whether it should be Animated or still, and press Generate. A generated scene can use everything the built-in ones use — layers at different depths, mountain ranges, sea swell, palms, rivers with a current, falling leaves, raindrop rings — and keeps to the same limits: the built-in scenes' colour budget, slow motion, nothing that could be mistaken for a node or a line. It is kept under Yours, shown first among the scene cards, with your account, so it is there on every device you sign in on (the 24 most recent). Each of your own scenes has a trash button that deletes it from Yours after asking; maps that already use it keep it.

Needs a miMind AI subscription; it is not part of the one-time trial.

A calm night sea under a crescent moon, with slow drifting mist Autumn leaves falling slowly through warm amber light Misty blue mountain ridges at dawn, the far ones barely moving

Ask the AI chat

In the chat panel, ask for a background and the assistant puts the built-in scene that fits best on your map, then asks what you think: Keep it, Try another (its next choice goes on, and the line under the reply shows which one you are on, such as 2/4), or, with a miMind AI subscription, Create a custom one, which designs a new scene from what you asked for. With that subscription, ask for something specific that no built-in scene shows and it designs one straight away. A scene designed in the chat goes behind the map and into Yours, just like one from Generate with AI, with Keep it and Generate another under it. You can also ask the assistant to take the scene away, or to make it slower, calmer, fainter or still. Every background change can be undone.

On a one-time chat trial without a subscription, the assistant only suggests a scene: it names one, with an Upgrade button, and leaves your map as it is.

Give this map a calm background Something wintry, please A background of lavender fields under a pale summer sky Make the background slower and a bit fainter Remove the background

External AI agents can pick a built-in scene too: for a new map with the background argument of the MCP server's create_map tool, and for an existing one with set_background, which miMind applies the next time you open that map.

MCP Server — connect external agents

miMind as a tool for Claude & other AI agents

The miMind MCP server lets external AI agents (Claude Code, Cursor, VS Code, Claude Desktop through the small mcp-remote bridge, and any MCP client that can send an access token; or claude.ai, Claude Desktop’s connectors and ChatGPT, by signing in with your miMind account) list, read, search and extend your synced maps, read them in depth (one node at a time, tasks and dates across your maps, or a whole map as JSON, Markdown, OPML or CSV), edit their nodes (add formatted nodes at an exact place, rename, restyle and move them; delete or replace only with your approval in the app), add content to them (text, links, pictures, videos, check boxes, lists, tables, charts, places, calendar cards and emoji, or text at the end of a note), give them a new look (layouts and their dials, themes and the canvas) and new central topics, link their nodes and restyle their lines, format them (fonts, emphasis, shapes, numbering and grouping; the words never change), tick their check boxes, fold their branches or focus one, copy branches, refine their style (spacing, the style sheet’s defaults or the theme’s, the glow and flowing lines), set the scene behind one and, from miMind 26.11.6, ask you to approve deleting or replacing parts of them or taking back an earlier request, and leave you messages, and, from miMind 26.11.6, build new maps from text or a template, rename, move and copy their files, make and rename folders, link one map to another, and ask you to approve moving a map to the trash; and, from miMind 26.11.6, read who is in the maps shared with you, their conversation, recent changes and version history, and ask you to approve restoring an earlier version; and, from miMind 26.11.6, export them as FreeMind, a web page, a JSON tree or CSV, list their dates as a calendar, read their tables, lists and links and a small picture of each, fill in their tables (and ask you to approve changing them), and save an export as a file on your device; and, from the next miMind update, find your maps by their words (word search, not semantic search: no AI model on our side), read and add the items inside notes, add drawings made from SVG, reorder content, set a saved or new scene and turn a title into a short list, with review mode if you want to approve every change first — with your permission, using personal access tokens, or apps you connect by signing in, which you can revoke or disconnect at any time, and read-only if you like. Agents never change your data directly: their changes are applied by miMind, at once while the map is open in an up-to-date app, and can be undone. They delete or replace something only with your approval in the app (from miMind 26.11.6, in the map’s Agent Requests). No agent deletes a file or a folder: a map leaves only through the trash, when you approve it, and nothing is ever written over a file or folder that is there. Connectors that sign in (claude.ai, Claude Desktop and ChatGPT) need no token; signing in is being switched on in stages, and so are many of the tools: until one is, it answers that it is not available at the moment. See the client recipes and the sixty-two tools.

The MCP server comes with miMind Business and miMind AI. It uses none of your AI allowance: the agent’s own AI (your Claude plan, for example) does the thinking, and miMind only reads and updates your maps.

Read the full MCP Server API reference →

Plans & Limits

PlanAI allowanceNotes
Free, Premium and BusinessNo AI allowanceThe AI assistant comes with a miMind AI plan. Business includes the MCP server, which uses no AI allowance. The app may offer a one-time trial instead (its Try button says how many maps or chat turns); a trial is used once and does not renew.
miMind AIA generous monthly token budget with a daily burst capRoughly 100+ full map generations or several hundred chat turns per month. Includes the MCP server. See Pricing.
Max plans5× the allowance of the matching Standard planmiMind AI comes in a Standard and a Max size. Max multiplies the monthly and daily limits by five for 4× the price; the features are identical. Pick the size with the Standard/Max switch on the pricing page; in the app, the switch appears once you have used a quarter of your monthly or daily allowance.

Your current usage is shown in Account → My Subscription, and on the usage meter next to the AI chat box — tapping the percentage explains how the allowance works and lets you move up to Max. Fair use applies; abusive automation may be limited.

AI & Your Data

What’s sent, and what we keep

miMind’s AI features are powered by Anthropic (Claude). AI requests go through miMind’s secure gateway to Anthropic; the app never calls Anthropic directly.

  • Only when you use AI, and only what the request needs. Generating a map sends your topic, pasted text or URL; generating a scene background sends your description of it, whether it should move, and whether the canvas is dark or light (a scene made with a new map sends that map’s title and the name of its theme in place of a description); chatting sends your message plus the outline of the open map (node titles and structure), which node you have selected, and which scene is behind the map along with the names of your own scenes in Yours; attachments send the images, PDFs, extracted file text, and links you add. When you supply a link, Claude may fetch that page and may search the web to answer.
  • We don’t store your prompts or the AI’s replies. Our gateway streams them to Anthropic and keeps only usage counts (tokens and request counts) for your plan’s limits — not the content. There is one exception, and you can delete it: the scene backgrounds you generate, which are kept in your account so that Yours is the same on every device you sign in on.
  • PDFs you attach in chat are held for up to 30 days. So that follow-up questions still work, a PDF attached in the chat panel is uploaded to Anthropic’s file storage and referenced by id on later turns, instead of being re-sent each time. We record only who owns each upload — never its contents — and a file can only ever be read back into your own conversations. Uploads are deleted automatically after 30 days. Attachments used for map generation are not stored at all: they travel with that one request.
  • Anthropic’s terms. We use Anthropic’s API under commercial terms under which your inputs and outputs are not used to train its models. See Anthropic’s Privacy Policy.
  • MCP sync is opt-in and publishes map outlines: each map’s title and its nodes’ titles and notes (the first 160 characters of each). From miMind 26.11.6 it also publishes a fuller copy of each map for your agents: titles up to 1,000 characters and notes up to 4,000, node colours, shapes and dates, check boxes with their labels, cross-links, and the web addresses of links and media (http or https only). Neither ever holds a file path on your device, your attachments, images or files (from miMind 26.11.6, the small picture of a map described below shows its images at low resolution). From miMind 26.11.6, encrypted maps are never published, and deleting a map or turning sync off can remove its copy (see the MCP guide). From miMind 26.11.6, once we switch them on, what an agent asks you to approve, and the messages agents leave, wait on our server until you answer or read them (at most 14 and 30 days) and are deleted at your app’s first sync 30 or more days after they end. From miMind 26.11.6, once our server shares them, the copies also say where each map’s file is (the drive, the folder and the file name, never the full path on your device) and which maps are open, so that agents’ file requests wait until you close a map (see where your files are); file requests wait on our server until your app does them (at most 7 days, 30 for a new map) and are deleted 30 days after they end, and the record of a map you let an agent move to the trash 90 days after it was trashed, or when it is recovered. Access tokens are stored only as hashes and are revocable at any time; apps you connect by signing in (once we switch it on) are listed on Manage Account, where you disconnect them, and revoking or disconnecting deletes them at once. From miMind 26.11.6, once we switch it on, an agent also reads, on your behalf, what you can see of a shared map your app published, with less about people (display names, never email addresses; the days people were last there, never where in the map they are), and the saved versions of your maps; versions saved with sync on also hold the copy agents read, and the owner of a shared map can hide it from every member’s agent (see maps shared with you). From miMind 26.11.6, once we switch them on, the copy agents read can also hold the cells of tables, list items, chart and calendar card titles and times, which of your maps a map links to and the size and type of its pictures and other media (never their names or files, and nothing about places), and a small picture of each map as you last closed it, left out as soon as you change the map; they are deleted with the copy. An export an agent asks for is saved as a new file in miMind’s exports folder on your device, never on a cloud drive, and its content never passes through our server (see rich content and exports). From the next miMind update, once we switch them on, our server also keeps with each copy a list of the words in it, in a simplified form that ignores capitals, accents and word endings, so agents can find maps by their words; it is made from the copy, never shown as such, deleted with the copy, and no AI model reads or processes it (see word lists and drawings).
  • Availability. Because our AI provider does not serve certain sanctioned countries, AI features are unavailable there; core miMind features are not affected.

Full details are in the miMind Privacy Policy. Only submit content you’re comfortable processing with a third-party AI service.