create-presentationLABSCO SUMMARY
A deck is a sequence of tool calls, and the last one is save.
This is a small, legible surface — one tool per slide layout, one folder for everything it writes, and an explicit save at the end. That last part is worth knowing before your first run: a client that stops early leaves you with a presentation in memory and no file on disk. Opening an existing deck writes backup.pptx before it touches anything, so editing something you care about is not a one-way trip.
What it is
An MCP server that creates PowerPoint presentations. You start or open a presentation by name, add slides one tool call at a time, and call save-presentation to write the file out. Everything is written into the --folder-path you pass at launch, and that folder is also where the server looks for images you want on a slide. Version 0.1.0, MIT licensed, run through uv from a clone.
What you get
create-presentation— starts a presentation object from anameopen-presentation— opens an existing deck for editing and automatically saves a copy asbackup.pptxfirstsave-presentation— writes the presentation into the folder path; the client has to call this to finalise the fileadd-slide-title-only— a title slide frompresentation_nameandtitleadd-slide-section-header— a section header fromheader, with an optionalsubtitleadd-slide-title-content— a title plus body contentadd-slide-title-with-table— a title plus a table built dynamically from adataarrayadd-slide-title-with-chart— a title plus a chart built from adataobject, with the chart type chosen from the shape of the dataadd-slide-picture-with-caption— a title, caption andimage_path, using either an image you placed in the folder or one this server generatedgenerate-and-save-image— creates an image from apromptusing the free FLUX model on TogetherAI
Requirements
uv and a clone of the repository. The client's command is uv, with --directory set to the path you cloned into, then run, powerpoint, and --folder-path set to the folder decks and images go in. --folder-path is not optional: every deck and image is written there, and any image you want placed on a slide has to already be in it. TOGETHER_API_KEY is needed only by generate-and-save-image; register for a key at api.together.xyz. Every other tool works without one.
Setup effort
Build from source — clone the repository, then follow the project's own run instructions
USE CASES
01
Turning the document you just discussed into slides
Start a presentation, add a title and a run of content slides as the assistant works through the source, and save it into your decks folder.
02
Putting query results on a slide instead of in a message
Hand over the rows and the server builds the table, or the chart, choosing a chart type from the data rather than asking you to pick one.
03
Adding a few slides to a deck that already exists
Open the file — a backup is written first — append the new section, and save; the client works with your existing pptx rather than a fresh one.
04
Illustrating a deck without hunting for stock images
Generate the image into the same folder from a prompt, then place it on a slide with its caption in the next call.
10 tools
Listed in project docs. Your client may show a different list.
add-slide-title-onlyadd-slide-section-headeradd-slide-title-contentadd-slide-title-with-tableadd-slide-title-with-chartadd-slide-picture-with-captionopen-presentationsave-presentationgenerate-and-save-imageBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Optional
TOGETHER_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/supercurses/powerpoint.gitMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"powerpoint": {
"command": "uv",
"env": {
"TOGETHER_API_KEY": "<YOUR_TOGETHER_API_KEY>"
},
"args": [
"--directory",
"<YOUR_PATH_TO_POWERPOINT>",
"run",
"powerpoint",
"--folder-path",
"<YOUR_PATH_TO_DECKS_FOLDER>"
]
}
}
}
