Mapify MCP Server
OfficialGenerates mind maps from YouTube videos, extracting and structuring content into visual maps.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Mapify MCP ServerCreate a mind map about quantum computing."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mapify MCP Server
Transform text, YouTube videos, and web content into beautiful mind maps using AI 🧠✨
The official Mapify Model Context Protocol (MCP) server enables AI assistants like Claude to generate interactive mind maps from various content sources. Built on the standardized MCP architecture, this server provides seamless integration between AI models and Mapify's powerful mind mapping capabilities.
✨ Features
🎯 Multi-Source Mind Mapping: Generate mind maps from text prompts, YouTube videos, websites, and documents
🔍 AI-Powered Search: Automatically search the web for keywords and create comprehensive mind maps from results
🌍 Multi-Language Support: Create mind maps in 15+ languages including English, Chinese, Japanese, Spanish, and more
📸 Visual + Interactive: Get both static images and editable mind map links
Related MCP server: Mind Map MCP
🔑 Getting Your API Key
Before using the Mapify MCP Server, you'll need to obtain your API token from the Mapify platform.
💡 Already have an account? Jump directly to your settings page and skip to Step 3.
Step 1: Create Your Account
Visit mapify.so and sign up for a free account.

Step 2: Access Main Dashboard
After logging in, you'll see the main Mapify dashboard with your mind maps and tools.

Step 3: Open Account Settings
Click on your profile/account menu to access your account settings.

Step 4: Generate Your API Token
Navigate to the "API Key" section and generate your API key. Copy and keep it secure!

🔒 Security Note: Treat your API key like a password. Never share it publicly or commit it to version control.
🚀 Quick Start
Prerequisites
Node.js (v16 or higher)
MCP-compatible client (Claude Desktop, VS Code, Cursor, Continue, etc.)
Installation
For Claude Desktop, add this configuration to your ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"mapify": {
"command": "npx",
"args": ["-y", "@xmindltd/mapify-mcp-server"],
"env": {
"MAPIFY_API_KEY": "your_api_token_here"
}
}
}
}📖 Usage Examples
Once configured, you can use these tools with your AI assistant:
Text-to-Mind-Map
Create a mind map about "Machine Learning fundamentals"AI Search to Mind Map
Create a comprehensive mind map for "climate change solutions 2025" by AI SearchYouTube Video Analysis
Generate a mind map from this YouTube video: https://youtube.com/watch?v=exampleWebsite Content Mapping
Create a mind map from the content on https://example.com/articleThe AI assistant will automatically:
🔄 Process your request using the appropriate Mapify tool
🌐 Search the web for relevant information
🎨 Generate a beautiful mind map image
🔗 Provide an editable link for further customization
📊 Return dimensions and metadata
🛠️ Manual Installation & Development
Local Setup
# Clone the repository
git clone https://github.com/xmindltd/mapify-mcp-server.git
cd mapify-mcp-server
# Install dependencies
pnpm install
# Build the project
pnpm run buildUsing Pre-built Binary
{
"mcpServers": {
"mapify": {
"command": "node",
"args": ["/absolute/path/to/mapify-mcp-server/build/index.js"],
"env": {
"MAPIFY_API_KEY": "your_api_token_here"
}
}
}
}🔗 Links
🌟 Mapify Platform: mapify.so
🐛 Report Issues: GitHub Issues
📖 MCP Specification: modelcontextprotocol.io
Ready to transform any ideas into visual mind maps? 🚀
Available Tools
1 toolgenerate_mindmapA
Generate a mind map from various inputs and provide both an image and an editable link
| Name | Required | Description | Default |
|---|---|---|---|
| prompt | Yes | The prompt to generate the mind map. When mode is website or youtube, the prompt should be a URL without any other text. | |
| mode | No | The mode to generate the mind map | prompt |
| language | No | The language of the mind map | en |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the output (image and editable link) which is helpful, but does not mention behavioral traits such as rate limits, authentication requirements, or potential side effects. The generation nature implies non-destructive behavior, but more detail would improve transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is concise and front-loaded with the main action. It avoids unnecessary words but could be restructured to list modes or highlight key output features without becoming overly long.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is relatively simple with 3 parameters and no output schema. The description mentions the output (image and editable link) which is useful, but does not explain the format of the link or any return values. For a basic generation tool, it is adequate but could be more complete by specifying what 'editable link' means.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description does not add additional meaning beyond what the schema already provides. The schema itself has clear descriptions for prompt, mode, and language, including instructions for mode-specific prompt usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool generates a mind map from various inputs and provides both an image and an editable link. It specifies both the action (generate) and the resource (mind map) along with the output format, making the purpose highly identifiable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide explicit when-to-use or when-not-to-use guidance. However, since there are no sibling tools, the need is reduced. The description implies usage for creating mind maps but lacks context on prerequisites or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.1- First observed
generate_mindmap
TDQS
Only one tool exists, so there is no risk of confusion or overlap. The tool's purpose is clear and unambiguous.
With a single tool, naming consistency is trivially achieved. The name 'generate_mindmap' follows a clear verb_noun pattern.
A single tool is too few for a service claiming to be a mind map server. Even for a minimal generative service, additional operations (e.g., retrieval, editing) are expected, making the surface feel incomplete.
The server only supports generating mind maps, lacking any tools for listing, viewing, updating, or deleting previously created maps. This is a significant gap for typical user workflows.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Create, edit, and organize MindMeister mind maps from your AI assistant.
Turn AI conversations into visual knowledge maps. Create, connect, search, and organize thoughts.
AI-powered diagrams, mind maps, flowcharts on a free unlimited collaborative whiteboard
Visual AI for strategic thinking — SWOT, flowcharts, mindmaps, Gantt diagrams as polished SVG.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables conversion of plain text descriptions and Markdown content into interactive mind maps using AI. Automatically uploads generated mind maps to Aliyun OSS and provides online access links.341MIT
- AlicenseBqualityDmaintenanceAutomatically generates mind map images from text content using Coze API workflow. Returns accessible image links that can be used in MCP-compatible tools like CodeBuddy, Cursor, and Qoder.12401MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to generate 3D models, textures, and images via the Meshy API using natural language, supporting text-to-3D, image-to-3D, remeshing, retexturing, rigging, and animation workflows.36601MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read and write XMind mind map files, allowing generation, editing, and analysis of mind maps directly in XMind.MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/xmindltd/mapify-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server