true-deck-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUE_DECK_OUTPUT_DIR | No | stdio mode: always also save decks here. | |
| TRUE_DECK_PUBLIC_URL | No | Base URL. Enables download_url; disables writing to caller-supplied paths. | |
| TRUE_DECK_ARTIFACT_DIR | No | Artifact cache (default ~/.cache/true-deck-mcp). | ~/.cache/true-deck-mcp |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deck_capabilitiesA | What this deck builder supports: slide kinds, body block types, capacity limits and the brand palette. Call this before writing deck Markdown for the first time. |
| deck_validateA | Parse deck Markdown and report the slide outline plus layout warnings (overflow risk, too many cards, missing titles) without rendering a file. Cheap — use it while drafting. |
| deck_generateA | Render deck Markdown into a True-branded .pptx. Returns an artifact_id — pass it to deck_preview to look at the result and to deck_fetch to get the bytes. Regenerate from edited Markdown rather than editing the .pptx. |
| deck_previewA | Render a generated deck to images so you can actually see it. Returns a contact sheet by default, or individual slides. Look for text spilling out of a card, a nearly empty slide, or a badly wrapped title, then fix the Markdown and regenerate. |
| deck_fetchA | Return the generated .pptx itself as an embedded resource, for hosts that cannot fetch a download URL. Large files are refused — use download_url or file_path instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_true_deck | Seed a conversation that produces a True-branded deck from a topic or notes. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| format_doc | Full Markdown authoring spec for True decks. |
| design_doc | Brand tokens, geometry and the layout engine. |
| example_doc | A complete worked example in the authoring format. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: capabilities provides metadata, validate checks Markdown, generate creates the PPTX, preview renders images, and fetch retrieves the file bytes. No overlap or ambiguity.
All tools share the 'deck_' prefix with a descriptive verb (fetch, validate, generate, preview), though 'deck_capabilities' breaks the verb pattern with a noun. The convention is still highly predictable and readable.
Five tools is well-scoped for a deck-building server: each tool covers a distinct step in the workflow from capability discovery to final artifact retrieval. No redundant or missing tools.
The tool surface covers the full lifecycle: understand constraints, validate drafts, generate the deck, visually preview it, and fetch the output. Regeneration is explicitly handled via Markdown editing, so no update/delete tools are needed.