mcp-pandoc-md2pptx
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert-contentsA | Converts Markdown content to PowerPoint (PPTX) format. šØ REQUIREMENTS:
ā Usage Example: 'Convert this markdown to PowerPoint and save as /presentations/demo.pptx' šØ PPTX STYLING:
ā”ļø Diagram Support:
š Creating Reference Documents:
|
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap. The tool's purpose is clearly defined and distinct.
The single tool 'convert-contents' uses a clear and descriptive verb_noun pattern. Consistency is not an issue with only one tool.
One tool is appropriate for a focused converter server. However, the tool must handle multiple aspects (templates, diagrams), which could justify additional tools for better separation.
The tool covers all necessary functionality for the Markdown-to-PPTX conversion use case: input format, template support, diagram rendering, and file output. No obvious gaps.