mindlm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Same as ANTHROPIC_API_KEY, for any OpenAI-compatible endpoint. | |
| OPENAI_BASE_URL | No | The endpoint used with `OPENAI_API_KEY`. | https://api.openai.com/v1 |
| ANTHROPIC_API_KEY | No | Switches `auto` to `llm` mode. | |
| MINDMAP_LLM_MODEL | No | Model name. Required for OpenAI-compatible endpoints, where no name is portable. | claude-sonnet-5 for Anthropic |
| MINDMAP_OUTPUT_DIR | No | Where exported HTML files go. `~` is expanded. | ./mindmaps |
| MINDMAP_LLM_PROVIDER | No | `anthropic` or `openai`. Inferred from whichever key is set. | auto-detected |
| MINDMAP_MAX_INPUT_CHARS | No | Hard cap on characters read from any one input. | 200000 |
| MINDMAP_CLIENT_MAX_CHARS | No | Cap on the source text returned in `client` mode. | 60000 |
| MINDMAP_ALLOW_PRIVATE_HOSTS | No | Let `url_to_mindmap` reach localhost and private networks. | false |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| text_to_mindmapA | Turn text or Markdown into a mind-map outline. Use this for content you already have — a draft, notes, a transcript, a chunk of a document. Returns a Markdown outline; pass export: true, or call export_mindmap afterwards, to get an HTML file. |
| url_to_mindmapA | Fetch an http(s) page (or a PDF served over http) and turn its main content into a mind-map outline. Article text is extracted with Readability; navigation and boilerplate are dropped. Pages that render entirely in JavaScript will come back empty — paste the text into text_to_mindmap instead. |
| pdf_to_mindmapA | Read a local PDF and turn it into a mind-map outline, using its bookmarks as the skeleton when it has them. Scanned PDFs with no text layer are rejected — there is no OCR. Use pages to limit long documents. |
| export_mindmapA | Render a Markdown outline into a standalone HTML mind map — interactive, single file, no network needed. Call this after you have written or refined an outline. Returns the file path; it does not overwrite an existing file unless you ask it to. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| mindmap_outline | The rules an outline must follow before export_mindmap renders it. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool maps to a clearly distinct input source (raw text, URL, local PDF) plus one distinct output operation (HTML export). The only mild overlap is url_to_mindmap also accepting remotely-served PDFs, but the descriptions explicitly differentiate remote vs. local handling.
Three tools share a clean {source}_to_mindmap pattern (text/url/pdf), and all four share the 'mindmap' suffix, making the set cohesive. export_mindmap deviates by using a verb_noun form rather than the source_to pattern, a minor inconsistency.
Four tools is compact and each earns its place: three input adapters and one exporter form a coherent pipeline. It leans slightly thin—no redundancy, but little room for edge operations—so not quite ideal.
The surface covers the core lifecycle: acquire content from text/URL/PDF, produce an outline, and render standalone HTML. Gaps are minor—no import of an existing outline file and no alternative export formats (PNG/SVG/OPML)—but agents can work around them.