Skip to main content

dcc-mcp-PowerPoint

PowerPoint adapter for the DCC-MCP ecosystem — the application layer over dcc-mcp-office: deck generation from structured content, slide composition, review decks from DCC renders, batch PDF conversion and text replacement (via the shared core), previews and visual validation.

Status: M1 + M2 authoring live. The designed pipeline runs end-to-end: Deck IR (office-ir/1.0) → Open XML compile (python-pptx) → desktop COM render (PowerPoint DispatchEx, dedicated instance) → PDF + per-slide PNG previews → structural validation. On top of generation, M2 adds structured deck modification (ppt-patch/1.0), smart semantic layers and a plugin registry — see the skill packs below. Skill scripts are executable through the dcc-mcp gateway (DCC_MCP_POWERPOINT_SKILL_PATHS). The shared C# host in dcc-mcp-office remains the production COM path (M1 there).

Part of the DCC-MCP host matrix

dcc-mcp-PowerPoint — PowerPoint adapter for DCC-MCP — deck generation (Deck IR → Open XML compile → COM render), slide composition and review decks.

It is one of 47 host adapters in the DCC-MCP catalog. Every adapter speaks the same MCP protocol and builds on the same core runtime contract; each one exposes the tools its own host needs on top of that.

This block is generated from the catalog entry in dcc-mcp-catalog.yml. Re-run the generator after changing the catalog.

Design (two-layer sidecar)

Agent → dcc-mcp-gateway (Rust, dcc-mcp-core)
          → dcc-mcp-server sidecar  (lifecycle: RFC #998)
              → office-host.exe --app=powerpoint  (C#, dcc-mcp-office)
                  → POWERPNT.EXE (COM, interactive user session)
  • Gateway + sidecar lifecycle: existing dcc-mcp-core machinery.
  • office-host: shared C# runtime from dcc-mcp-office (download/verify/launch via dcc-mcp-release-artifacts).
  • This repo owns: PowerPoint IR semantics, powerpoint.deck.generate / powerpoint.slide.compose / powerpoint.slide.render, template registry entries, and the PowerPoint skill packs.

Skill packs

  • powerpoint-deck — generate an editable deck from structured content (template → semantic layouts → IR → Open XML → COM finalize → previews → validation loop; proposal §15.3/§15.4). Generated decks are tagged with six semantic layers (background/decoration/header/content/accent/footer).
  • powerpoint-edit — modify existing decks with a structured patch document (ppt-patch/1.0): text, notes, pictures, fills/lines, visibility, shape deletion, slide add/delete/move (new slides compile from Deck IR layouts) and layer assignment. All-or-nothing saves.
  • powerpoint-layers — smart semantic layers over shapes (native ::layer=<name> name tags): list, show/hide, restack z-order (front/back/above/below) and recolor per layer.
  • powerpoint-plugins — discover and invoke user-installed plugins (plugin.json manifest + stdin-JSON script contract, subprocess isolation, timeout caps).
  • powerpoint-review — dcc.review-deck-from-renders: build review decks from Maya/Houdini/Blender/Unreal renders + shot/asset metadata (proposal §15.7).

Capability-boundary showcase

examples/capability_boundary_showcase.json is a 17-slide deck that walks every semantic layout and the M2 capability surfaces: generation (IR → Open XML → COM render → validation), smart layers (list / visibility / recolor / reorder / assign), the patch engine (7-operation ppt-patch/1.0 with all-or-nothing saves) and the plugin registry (deck-stats demo plugin in examples/plugins/). See examples/output/capability-boundary/README.md for the full runbook and artifact map.

Agent usage (via dcc-mcp-cli / gateway)

  1. Start the registered adapter (the launcher binds the bundled skill packs and script runtime to the official dcc-mcp-server): dcc-mcp-powerpoint serve
  2. Run a skill script directly (gateway execute_script contract — stdin JSON or CLI flags):
    python src/dcc_mcp_powerpoint/skills/powerpoint-deck/scripts/generate_deck.py \
      --input examples/dcc_mcp_framework_intro.json --out out
    
  3. Validate the packs with the official linter:
    dcc-mcp-cli lint src/dcc_mcp_powerpoint/skills --warnings-as-errors --non-interactive
    

Development

pip install -e .[dev,sidecar]
pytest

License

MIT

Metadata

Release files for dcc-mcp-powerpoint 0.2.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dcc-mcp-powerpoint 0.2.4
File Size Uploaded
dcc_mcp_powerpoint-0.2.4.tar.gz 16.7 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for dcc-mcp-powerpoint 0.2.4
File Interpreter ABI Platform
dcc_mcp_powerpoint-0.2.4-py3-none-any.whl Python 3 none any Details

Total release size: 17.1 MB

Release files / dcc_mcp_powerpoint-0.2.4.tar.gz

Download URL dcc_mcp_powerpoint-0.2.4.tar.gz
Size 16.7 MB
Tags Source
SHA-256 checksum
How to use checksums
402810fac7e82de32d3c9bf68605ab3bbb25a8ff6ef9b8f02a8066b8d43a22e7
BLAKE2b-256 checksum
How to use checksums
4ef18af7527f718b6598d0f1f622d1054fe65fd61f4bc8b817dc59c6984ab1b5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / dcc_mcp_powerpoint-0.2.4-py3-none-any.whl

Download URL dcc_mcp_powerpoint-0.2.4-py3-none-any.whl
Size 379.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
001b19131f9c249eb3fae1a737c0987a6bad1d21b18ad60d6e8a6f4f82ecf8bb
BLAKE2b-256 checksum
How to use checksums
4b7a8f88028683e2277f107a56bb0a24669cdec6ac0f220573494994b56801f1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.4 This release

2 release files

0.2.3

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page