Mapify MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAPIFY_API_KEY | Yes | Your Mapify API key obtained from the Mapify platform settings. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_mindmapA | Generate a mind map from various inputs and provide both an image and an editable link |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.