Converts Markdown content to PowerPoint (PPTX) presentations while preserving formatting and structure, with support for custom templates and styling
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-pandoc-md2pptx Convert my meeting notes to a presentation and save it as /presentations/team-update.pptx"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol server for converting Markdown content to PowerPoint (PPTX) presentations using pandoc.
This MCP server provides a simple tool to transform Markdown content into PowerPoint presentations while preserving formatting and structure. Perfect for creating presentations from documentation, notes, or any Markdown content.
Related MCP server: Deckbuilder MCP Server
convert-contents
Converts Markdown content to PowerPoint (PPTX) format
Inputs:
contents (string): Markdown content to convert (required if input_file not provided)
input_file (string): Path to Markdown input file (required if contents not provided)
output_file (string): Complete path for PPTX output file (required)
template (string): Path to a template PPTX document to use for styling (optional)
{
"mcpServers": {
"mcp-pandoc-md2pptx": {
"command": "uvx",
"args": ["mcp-pandoc-md2pptx"]
}
}
}Pandoc Installation
# macOS
brew install pandoc
# Ubuntu/Debian
sudo apt-get install pandoc
# Windows
# Download from: https://pandoc.org/installing.htmlUV Package Installation
# macOS
brew install uv
# Windows/Linux
pip install uv"Convert this markdown to PowerPoint and save as /presentations/demo.pptx:
# My Presentation
## Slide 1
Content here""Convert /path/to/input.md to PPTX and save as /path/to/output.pptx""Convert markdown to PPTX using /templates/theme.pptx as template and save as /presentations/styled.pptx"Create custom PowerPoint templates for consistent branding:
Generate default template:
pandoc -o template.pptx --print-default-data-file reference.pptxCustomize in PowerPoint with your fonts, colors, and slide layouts
Use in conversion:
"Convert content using /path/to/template.pptx as template"Add to your Claude Desktop config:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-pandoc-md2pptx": {
"command": "uvx",
"args": ["mcp-pandoc-md2pptx"]
}
}
}npx -y @smithery/cli install mcp-pandoc-md2pptx --client claudeuv run pytestuv sync
uv builduv publishReport Issues: GitHub Issues
Submit Pull Requests: Improve the codebase or add features
Special thanks to MCP Pandoc and pandoc-ext/diagram
Simple, focused Markdown to PowerPoint conversion via MCP
Converts Markdown content to PowerPoint (PPTX) format.
๐จ REQUIREMENTS:
Input: Only Markdown format is supported
Output: Only PPTX format is supported
File Path: Complete output path with filename and .pptx extension is required
โ Usage Example: 'Convert this markdown to PowerPoint and save as /presentations/demo.pptx'
๐จ PPTX STYLING:
Use template parameter to apply custom PowerPoint templates
Create templates with your branding, fonts, and slide layouts
Example: 'Convert markdown to PPTX using /templates/theme.pptx as template and save as /presentations/pitch.pptx'
โก๏ธ Diagram Support:
Diagram using mermaid, plantuml, graphviz is supported by default. Referencing external resource in plantuml is also supported.
Example:
@startuml Two Modes - Technical View
' Uncomment the line below for "dark mode" styling
'!$AWS_DARK = true
!define AWSPuml https://raw.githubusercontent.com/awslabs/aws-icons-for-plantuml/v20.0/dist
!include AWSPuml/AWSCommon.puml
!include AWSPuml/AWSSimplified.puml
!include AWSPuml/General/Users.puml
!include AWSPuml/NetworkingContentDelivery/APIGateway.puml
!include AWSPuml/SecurityIdentityCompliance/Cognito.puml
!include AWSPuml/Compute/Lambda.puml
!include AWSPuml/Database/DynamoDB.puml
left to right direction
Users(sources, "Events", "millions of users")
APIGateway(votingAPI, "Voting API", "user votes")
Cognito(userAuth, "User Authentication", "jwt to submit votes")
Lambda(generateToken, "User Credentials", "return jwt")
Lambda(recordVote, "Record Vote", "enter or update vote per user")
DynamoDB(voteDb, "Vote Database", "one entry per user")
sources --> userAuth
sources --> votingAPI
userAuth <--> generateToken
votingAPI --> recordVote
recordVote --> voteDb
@enduml๐ Creating Reference Documents:
Generate PPTX template: pandoc -o template.pptx --print-default-data-file reference.pptx
Customize in PowerPoint: fonts, colors, slide layouts
| Name | Required | Description | Default |
|---|---|---|---|
| contents | No | Markdown content to be converted (required if input_file not provided) | |
| input_file | No | Complete path to Markdown input file (e.g., '/path/to/input.md') | |
| output_file | No | Complete path where to save the PPTX output including filename and .pptx extension (required) | |
| template | No | Path to a template PPTX document to use for styling |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the burden. It discloses key behaviors: supports only Markdown input and PPTX output, requires complete file paths, supports diagram types (mermaid, plantuml, graphviz), and template usage. No contradictions. It could mention error handling or file size limits, but overall transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is moderately long but well-structured using headings, bullet points, and examples. Every section adds value (requirements, examples, diagram support, template creation). The core purpose is front-loaded, and the format is scannable. Could be slightly more concise, but effective.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (4 params, no output schema, no siblings), the description covers all necessary aspects: input/output formats, file path requirements, template usage, diagram support, and even how to generate templates. It provides complete guidance for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 100% description coverage, so baseline is 3. The description adds significant value beyond schema: explains the oneOf relationship between contents and input_file, provides real usage examples for template, and details diagram support. This extra context justifies a score of 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'Converts Markdown content to PowerPoint (PPTX) format.' It clearly identifies the input format (Markdown), output format (PPTX), and the tool's action, leaving no ambiguity. With no sibling tools, differentiation is irrelevant, but the description is exceptionally clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit requirements: input must be Markdown, output only PPTX, complete file path required. It includes usage examples and mentions template and diagram support. While it lacks explicit 'when not to use' or alternative tools (none exist), the context is very clear and practical.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Generate PDF, Word (.docx) and PowerPoint (.pptx) documents from Markdown over MCP.
Generate professional PowerPoint presentations from text, YouTube videos, or structured JSON data.โฆ
Use your own Word templates to convert Markdown โ DOCX/PDF/HTML from any MCP-compatible AI.
Generate, render, and host Slidev presentations from markdown
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/maekawataiki/mcp-pandoc-md2pptx'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
