Presentation Artifact Generation Engine (MCP Endpoint)

This service exposes functionality via the Model Context Protocol (MCP) to enable automated creation and manipulation of native PowerPoint presentation files. It furnishes a robust interface allowing AI constructs or client applications to dynamically assemble and revise deck content.

Core Capabilities

• Instantiation of novel PowerPoint document instances.
• Loading and modification of extant PPTX archives.
• Procedures for augmenting slide counts and editing existing slide layouts.
• Insertion mechanisms for heterogeneous content: textual passages, visual assets, tabular data structures, and charting elements.
• Enforcement of uniform aesthetic properties via reference to a defined style schema.
• Provision of a standardized API accessible through the MCP framework.

System Architecture Blueprint

mcp_engine/ ├── main_entrypoint.py # Primary execution starter (Renamed from main.py) ├── configuration_handler.py # Handles environment and style parameter loading (New component) ├── deck_composer.py # Core module responsible for slide construction logic (Renamed from ppt_generator.py) ├── AUTOMATION_GUIDE.md # Documentation file (Renamed from README.md) ├── dependencies.txt # Manifest of required external packages ├── assets/ # Directory for input materials │ ├── slide_payload.json # Definition of slide content structure (Relocated from data/slide_content.json) │ └── visual_schema.json # Design parameter definitions (Relocated from data/design_system.json) ├── artifacts/ # Repository for finalized output files └── support_routines/ # Helper functions and utility libraries (Maintained structure)

Operational Sequence

1. Execution commences at the designated entry point (main_entrypoint.py).
2. System parameters and visual styling directives are retrieved via configuration_handler.py.
3. deck_composer.py processes the content payload and executes the primary document synthesis.
4. Manipulation of the presentation structure leverages functions within the support_routines namespace.
5. The finalized document is committed to the artifacts directory.

Deployment Prerequisites

Dependencies

• Minimum Python environment version 3.6.
• python-pptx library dependency.
• MCP framework client utilities.

Installation Steps

# Install necessary software components
pip install python-pptx mcp[cli]

Execution Instructions

Initiating the MCP Endpoint Server

python main_entrypoint.py

The service defaults to operation on port 8000 at the local interface. Alternate network binding parameters can be supplied via:

python main_entrypoint.py --interface 0.0.0.0 --port 8080

Running Diagnostic Clients

python verification_script.py

Available Interaction Methods

Document Lifecycle Procedures

• initiate_new_deck: Constructs a blank presentation canvas.
• load_existing_deck: Obtains and opens a previously saved presentation file.
• commit_deck_state: Serializes and saves the current presentation state.

Slide Management Procedures

• append_new_slide: Adds a subsequent slide boundary to the deck.
• inject_slide_payload: Places specified content constructs onto a designated slide.
• itemize_slide_content: Inserts structured enumerations (bullet points) onto a slide surface.

Template-Based Generation

• synthesize_from_blueprint: Generates a presentation using a predefined template file synchronized with input data.

Troubleshooting Guide

• Error: Module Not Found: Verify prerequisite installation via the pip install python-pptx mcp[cli] command.
• Error: Service Binding Failure: Investigate port occupancy conflicts; attempt reassignment of the network port.
• Error: Output Persistence Failure: Check filesystem permissions for the designated output path and confirm directory existence.

Data Structure Schemas

Slide Content Definition (JSON Payload)

Structure expected within assets/slide_payload.json:

{
  "deck_title": "Presentation Master Title",
  "primary_sections": {
    "Section_A": {
      "Subsection_A1": { ... },
      "Subsection_A2": { ... }
    },
    "Section_B": [ ... ]
  }
}

Visual Styling Directives (JSON Schema)

Structure expected within assets/visual_schema.json:

{
  "slide_typographic_settings": {
    "title_typeface": "Calibri",
    "title_size_pt": 40,
    ...
  },
  "matrix_render_styles": {
    "standard": {
      "header_color_rgb": [150, 150, 150],
      ...
    }
  },
  ...
}

Customization Vectors

Content Refinement

Alterations to presentation narrative are managed by modifying the data structure within assets/slide_payload.json.

Aesthetic Modification

Design themes and graphical parameters are tunable by editing the configuration map located in assets/visual_schema.json.

Source Code Adaptation

Procedural adjustments to how slide components are synthesized can be made by revising the following methods within deck_composer.py:

• _render_cover_slide: Logic for constructing the introductory slide.
• _process_major_sections: Logic for rendering thematic segment slides.
• _render_detail_slide: Logic for rendering subordinate concept slides.
• _construct_definition_grid: Logic for rendering term reference tables.
• _build_enumerated_listing: Logic for rendering sequential lists.