Skip to main content
Glama
true-deck-mcp

true-deck-mcp

by ramzpat

true-deck-mcp

An MCP server that turns Markdown into True Corporation branded PowerPoint decks. Same renderer as the true-deck skill — one template, two front doors.

See DESIGN.md for the architecture and the interactive-app plan.

Install

pip install -e .            # or: pip install mcp>=2.0.0 python-pptx pillow

Preview rendering additionally needs LibreOffice and poppler:

apt-get install -y libreoffice-impress poppler-utils

Without them everything except deck_preview still works, and deck_capabilities reports preview_available: false.

Related MCP server: marp-agent-mcp

Run

# local, for Claude Code / Claude Desktop / Gemini CLI
python -m true_deck_mcp --output-dir ~/Decks

# remote, for a Claude custom connector
python -m true_deck_mcp --transport http --port 3333 \
  --public-url https://decks.example.com

Env var

Meaning

TRUE_DECK_PUBLIC_URL

Base URL. Enables download_url; disables writing to caller-supplied paths.

TRUE_DECK_OUTPUT_DIR

stdio mode: always also save decks here.

TRUE_DECK_ARTIFACT_DIR

Artifact cache (default ~/.cache/true-deck-mcp).

Connect

Claude Code / Claude Desktop — claude_desktop_config.json or .mcp.json:

{
  "mcpServers": {
    "true-deck": {
      "command": "python",
      "args": ["-m", "true_deck_mcp", "--output-dir", "/Users/you/Decks"],
      "env": { "PYTHONPATH": "/path/to/true-deck-mcp/src" }
    }
  }
}

Claude web / Cowork — run with --transport http, expose it (npx cloudflared tunnel --url http://localhost:3333 for a quick test), then Settings → Connectors → Add custom connector → https://.../mcp.

Gemini Spark — Settings & help → Connected Apps → add the server URL. Tools work; interactive UI is not documented there, so the server's text results are what you get.

Tools

Tool

What it does

deck_capabilities

Slide kinds, block types, capacity limits, palette.

deck_validate

Outline + layout warnings, without rendering. Fast.

deck_generate

Markdown → .pptx; returns an artifact_id.

deck_preview

Renders the deck to PNGs so the agent can see it.

deck_fetch

Returns the .pptx as an embedded base64 blob.

Resources: deck://format, deck://design-spec, deck://example. Prompt: build_true_deck(topic).

Typical agent loop

deck_capabilities()                     → learn the format (once)
deck_validate(markdown)                 → fix warnings
deck_generate(markdown, "board.pptx")   → artifact_id
deck_preview(artifact_id)               → LOOK AT IT
   ...edit the Markdown, regenerate...
deck_fetch(artifact_id) / download_url  → hand it over

Test

python3 tests/test_e2e.py

Spawns the server over real stdio and exercises every tool, writing the resulting deck and contact sheet to /tmp/true-deck-e2e.

Available Tools

5 tools
deck_capabilitiesDeck capabilitiesA
Read-only

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.

Inputs: no named parameters.

deck_fetchFetch deck fileA
Read-only

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.

Inputs: artifact_id (required).

deck_generateGenerate deckA
Idempotent

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.

Inputs: markdown (required), save_to, filename. Returns: filename, warnings, file_path, mime_type, +7 more

deck_previewPreview deckA
Read-only

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.

Inputs: artifact_id (required), dpi, mode, slides.

deck_validateValidate deck MarkdownA
Read-only

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.

Inputs: markdown (required). Returns: ok, meta, slides, warnings, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Related MCP Connectors

    Related MCP Servers