PPTX Generator MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_presentationB | Generate a PPTX presentation from markdown content. Returns path to the generated file. |
| get_templateB | Get an example markdown template showing the correct format for creating presentations |
| get_configB | Get current presentation configuration (colors, fonts, instructor info) |
| update_instructorC | Update instructor information in the configuration |
| list_presentationsB | List all generated presentations in the output folder |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: generate_presentation creates new presentations, get_config retrieves configuration, get_template provides formatting examples, list_presentations enumerates existing files, and update_instructor modifies specific configuration data. The boundaries between these operations are unambiguous.
All tools follow a consistent verb_noun pattern with snake_case naming (generate_presentation, get_config, get_template, list_presentations, update_instructor). The verbs appropriately describe each action (generate, get, list, update) without deviation or mixing of conventions.
Five tools is well-scoped for a presentation generation server, covering the core workflow: template guidance, configuration management, generation, and output listing. Each tool earns its place without redundancy or excessive specialization for this domain.
The toolset covers the essential presentation generation workflow from template to output, but lacks update/delete operations for generated presentations or broader configuration management beyond instructor info. Agents can work around these minor gaps, but the surface isn't fully comprehensive.