pptx-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| pptx_outlineB | Turns a .pptx into a slide-by-slide outline: title, body text and speaker notes, as JSON. |
| pptx_thumbnailB | Returns the cover thumbnail image that PowerPoint saved inside the .pptx, if there is one. |
| pptx_web_previewA | Writes a self-contained HTML page previewing the first 5 slides as text cards, ready to share. |
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 3 tools
Each tool targets a distinct output: JSON outline, cover thumbnail image, and HTML preview page. pptx_outline and pptx_web_preview both surface slide text, so an agent might briefly weigh one against the other, but the format/naming distinction (JSON vs HTML, all slides vs first 5) clarifies intent.
All three tools use an identical pattern: the pptx_ prefix plus a snake_case noun/descriptor. Fully predictable and readable.
Three tools is a small but coherent set for a read-only pptx inspection server. It is on the lean side, but each tool earns its place without redundancy.
Coverage is entirely read-only: no creation, editing, or slide/image extraction beyond the saved cover. The web preview also caps at the first 5 slides, a notable gap for a complete inspection surface.