mmm-mcp-server
Related Servers
Alternatives to mmm-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to build and interact with mind maps on mindmap.io. Agents can create, read, update, and delete maps and nodes, run prompts on nodes, and auto-expand topics into follow-up questions.13MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, read, convert, validate, and render .xmind mind maps, including PNG/SVG/HTML output and compatibility with the official Xmind client.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read and write XMind mind map files, allowing generation, editing, and analysis of mind maps directly in XMind.MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to read and edit XMind mind maps, including OCR for images embedded in nodes.MIT

Maito MCP Serverofficial
AlicenseBqualityDmaintenanceEnables AI assistants to interact with Maito workspaces for task management, note-taking, and planning.2114 npmAGPL 3.0- AlicenseAqualityBmaintenanceEnables AI assistants to read and edit a spatial canvas board of notes, tasks and ideas through the running desktop app, creating, updating, linking, grouping and arranging nodes, importing files, focusing the view and undoing changes so edits appear instantly and stay reversible.2510 npm1MIT
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes (move_element, edit_element, set_schedule, update_task_status, delete_elements each target a different mutation). The main overlap is auto_structure_thought vs import_markdown_context, which both write hierarchical content into an existing map, but the descriptions differentiate them well (Claude-generated structure vs Markdown import).
All names use snake_case with a verb-first pattern (list_maps, create_map, edit_element, move_element, delete_elements, set_schedule, sign_in). Minor deviations: singular/plural inconsistency (move_element vs delete_elements) and auto_structure_thought, which is adverb_verb_noun rather than a clean verb_noun.
11 tools is well within the ideal 3-15 range and each tool corresponds to a real operation (map CRUD-ish, element mutation, scheduling, import, auth). No filler tools and no missing obvious operation that would need bundling.
The element lifecycle is well covered: create map, list maps/elements, add structure, import, edit text, move, delete, toggle task state, set schedule, plus sign-in. Gaps are at the map level (no rename_map or delete_map) and there is no direct single-element create outside structure/import, but agents can work around these.