plan-export-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUPPETEER_EXECUTABLE_PATH | No | Path to the Chrome/Chromium executable. Used when Puppeteer cannot locate Chrome automatically. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| export_planA | Export an AI agent implementation plan or audit (Markdown) to styled PDF, high-res PNG, or self-contained HTML matching IDE aesthetics. |
| render_diagramA | Render an isolated Mermaid diagram (sequence, flowchart, class, architecture, ER) directly to a cropped PNG or SVG file with optional visual preview in chat. |
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 2 tools
The two tools target different output types and inputs: one exports whole Markdown plans/audits, the other renders isolated Mermaid diagrams. There is mild potential for confusion when a plan includes diagrams, but the descriptions make the boundary clear.
Both tools follow the same verb_noun pattern: export_plan and render_diagram. The naming is parallel, predictable, and accurately reflects each tool's function.
With only two tools, the server feels thin but is still reasonably scoped for a narrow plan-export and diagram-rendering purpose. It is not bloated, yet it sits at the lower boundary of acceptable tool count.
The core workflows are covered: exporting plans to common document formats and rendering diagrams to image formats. Minor gaps exist, such as batch processing or combining plan text and diagrams into a single export, but agents can accomplish the primary tasks without dead ends.