pptx-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PPT_MCP_OUTPUT_DIR | No | Optional output directory for generated .pptx files when no outputPath is provided and the MCP client does not support roots. | ~/Documents/PPT-MCP |
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 |
|---|---|
| preview_slideA | DESIGN-ITERATION TOOL ONLY. Renders a single complete HTML document to a PNG image and saves it to disk, returning the file path (not the image data). Open/view that PNG file with whatever image-reading capability your agent has to check the design — this tool does NOT produce a .pptx and is NOT how a presentation gets delivered. Use it only to check how one slide looks while you're still tweaking its HTML/CSS. Once the user's slides are finalized, you MUST call build_pptx to actually produce the .pptx file — that is the only tool that creates a deliverable presentation file. |
| build_pptxA | THE DELIVERABLE TOOL. Renders a list of complete HTML documents (one per slide) and assembles them into a single PowerPoint (.pptx) file written to disk, one image-backed slide per HTML input, in order. Call this — not preview_slide — whenever the user asks for a PPT/PowerPoint/presentation/apresentação/slide deck; the tool result gives you the saved file path to report back to the user. |
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
preview_slide is explicitly scoped to single-slide PNG design checks, while build_pptx is the only tool that produces the deliverable PPTX. The descriptions draw a clear boundary and even warn against using preview_slide for final delivery.
Both tools follow the same verb_noun pattern: preview_slide and build_pptx. The naming is consistent, predictable, and each verb clearly indicates the action.
Two tools is slightly lean relative to the typical 3-15 range, but the server's scope is deliberately narrow: preview a slide and build a deck. Each tool earns its place and there is no redundancy.
The workflow is complete for the stated purpose: preview_slide covers design iteration and build_pptx covers final deliverable creation from a list of HTML slides. There are no obvious missing operations in this focused domain.