DeckCraft MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DECKCRAFT_APP | No | Path of the desktop app when it lives elsewhere (e.g. a Linux AppImage) | |
| DECKCRAFT_CLI | No | Path of deckcraft-cli / deckcraft-cli.exe (wins over DECKCRAFT_DIR) | |
| DECKCRAFT_DIR | No | DeckCraft folder, one of its executables, a .tar.gz root (with bin/) or DeckCraft.app. Default: auto-detect | |
| DECKCRAFT_MCP_TIMEOUT | No | Maximum seconds per engine call (default 3600) | 3600 |
| DECKCRAFT_CONTROL_PORT | No | Control port of the desktop app (default 7990) | 7990 |
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 |
|---|---|
| create_presentationB | Build a slide deck with DeckCraft (a PowerPoint-class presentation app) from a list of slides: title, subtitle, bullets with levels (one or two columns), a picture, a chart (column, bar, line, pie, doughnut, area, scatter...), a table, shapes and text boxes, speaker notes, background colour, transition and bullet animation; theme, colour and font schemes, slide size, slide numbers and footer. Or from a plain-text outline (one slide per top-level line). Saves PowerPoint pptx, pdf (slides, notes or handouts), deckcraft, png / jpeg per slide or an outline, and returns pictures of the first slides to check them. |
| edit_presentationA | Open PowerPoint or DeckCraft presentations (one, a list or a folder) and change them: find and replace text in titles, text boxes, shapes and table cells, apply a theme, colour or font scheme, add slides (same description as create_presentation) at a position, delete slides, set speaker notes, transitions, slide numbers and footer. Saved as new copies; the originals are only read. |
| convert_presentationB | Convert PowerPoint (.pptx) or DeckCraft (.deckcraft) presentations (one, a list or a folder) to pdf (slides, notes pages or handouts), pptx, deckcraft, png / jpeg images of every slide, or a text outline. |
| get_presentation_infoA | Slides of a PowerPoint or DeckCraft file: titles, layouts, every shape with its id, kind, box and text, tables, charts, speaker notes, transitions and animations, plus theme, fonts, slide size and sections. Optionally a spelling and accessibility review. |
| render_slidesB | Pictures of slides of a PowerPoint or DeckCraft file to look at them: up to 8 images and, with save=true, PNG files (_s.png). |
| list_deckcraft_catalogB | What DeckCraft can do: commands (the engine commands with parameters and ribbon place, for run_deckcraft_commands), themes (themes, colour schemes and font schemes), layouts, shapes (preset names), transitions, animations (effects) and formats. |
| run_deckcraft_commandsA | Advanced: run any DeckCraft engine commands in order (slide., shape., text., format., design., transition., animation., table., chart., insert., picture., comment., section.*...) plus the engine tools add_slide / go_to_slide / add_shape / add_text_box / set_text / insert_picture / insert_table / insert_chart / inspect_slide / inspect_document / select / key / type_text (step id = the tool name), on a new or an opened presentation, then save. Coordinates are points (16:9 = 960×540). Parameters can use "$steps[N].field" for a value returned by step N (0-based). With live=true the steps drive the open DeckCraft app instead. |
| open_in_deckcraftA | Open presentations in the DeckCraft desktop app to present or keep editing by hand. With control=true the app also starts its loopback-only control channel so run_deckcraft_commands live=true can drive it. |
| get_deckcraft_statusA | Check the DeckCraft installation: platform, executables, version, engine commands, themes, formats, whether the app is running / listening for control. |
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 9 tools
Each tool has a fairly distinct purpose (create, edit, convert, inspect, render, catalog, open, status). There is some overlap: run_deckcraft_commands can add slides/shapes that create_presentation and edit_presentation also handle, and render_slides overlaps with the preview images create_presentation returns. Descriptions largely clarify the boundaries, so ambiguity is limited.
Mostly verb_noun but the subject noun switches inconsistently between 'presentation', 'deckcraft', and 'slides' (create_presentation, render_slides, run_deckcraft_commands, get_deckcraft_status). The mixed subject and multi-word constructions break a single predictable pattern, though names remain readable.
Nine tools is a well-scoped set for a presentation engine. Each tool covers a distinct workflow (lifecycle, inspection, rendering, catalog, app control) with no filler.
The surface covers the full lifecycle: create, edit, convert, inspect, render, open, and an advanced escape hatch via run_deckcraft_commands plus catalog/status discovery. Minor gaps exist (no dedicated delete/duplicate-file operation), but these can be worked around through edit_presentation or the command runner.