mindspark-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server (default 3300). Only used when running over HTTP. | 3300 |
| MINDSPARK_APP_URL | No | URL where the MindSpark app is hosted. Used for the 'Open in MindSpark' link in the render_map widget. | |
| MINDSPARK_GH_REPO | No | GitHub repository name to store maps. Default is 'mindspark-maps'. | mindspark-maps |
| MINDSPARK_GH_TOKEN | No | GitHub personal access token (fine-grained or classic). Required if not using self-hosted mode. | |
| MINDSPARK_MCP_TOKEN | No | Optional token for HTTP transport. When set, requests must include Authorization: Bearer <token>. | |
| MINDSPARK_SELF_HOSTED_URL | No | Base URL of a self-hosted MindSpark server (e.g., http://localhost:3000). Required if not using GitHub mode. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_mapsA | List all of the user's mind maps, with id, title, and last-updated time. |
| get_mapA | Fetch a mind map by id and render it as an indented outline, so its structure and content are readable at a glance. |
| render_mapA | Render a mind map as an interactive visual diagram inline in the conversation, instead of plain text. Use this when the user asks to see, view, or visualize a map — get_map is better when you just need to read or reason about its contents. |
| create_mapA | Create a new mind map from a Markdown outline (headings and/or nested bullets). This is the preferred way to build a map from scratch — write normal Markdown (the way you already would) rather than constructing nodes one at a time. The first line becomes the map's central topic. Supports bold, italic, and |
| add_nodeA | Add a single new node under an existing node in a map. Use get_map first to find the parent node's id. |
| update_nodeA | Change the text, color, list style, or task status of an existing node. |
| delete_nodeA | Delete a node and its entire subtree. Cannot delete the root node — delete the whole map instead. |
| delete_mapA | Permanently delete an entire map. This cannot be undone through this tool (the file history remains in git, recoverable manually). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mindmap_widget | Interactive visual rendering of a MindSpark map |
TDQS
Scored across 8 tools
Each tool targets a distinct resource/action pair: maps vs nodes, listing vs rendering vs creating vs deleting. get_map and render_map could overlap, but the descriptions explicitly separate outline reading from visual rendering.
All tool names follow a consistent verb_noun pattern: list_maps, get_map, render_map, create_map, add_node, update_node, delete_node, delete_map. The verbs are clear and the object is always the affected resource.
Eight tools is well-scoped for a mind map management server. Each tool covers a necessary core operation without redundancy or bloat.
The surface covers the main lifecycle: list, read, render, create, update nodes, add nodes, delete nodes, and delete maps. Minor gaps exist around reorganizing nodes (move/reorder) and updating map-level metadata, but agents can accomplish core workflows.