office-powerpoint

Office-PowerPoint-MCP provides a set of tools to create, analyze, and modify PowerPoint presentations (.pptx) through MCP-compatible clients. It exposes core operations for managing presentations (create, read, list, and convert to PDF), content building (add slides, text boxes, images, charts, and tables), and design tasks (themes, slide layouts, text formatting, and animations). AI agents can invoke these tools to assemble professional slides, extract structure and metadata, apply branding through templates and themes, and export final outputs for reports or pitches. Clients like Claude Code or Amazon Q Developer can integrate these tools by configuring the MCP server as a remote capability provider and then issuing the corresponding function calls in their MCP workflows. The API surface includes operations such as create_presentation, get_presentation_info, list_available_presentations, convert_to_pdf, add_slide, add_text_box, add_image, add_table, add_chart, apply_theme, set_slide_layout, format_text, and add_animation. This enables end-to-end automation from slide planning to polished delivery, with support for layouts, media, and interactive elements. To use it, point your MCP client at the uvx-based server (as shown in the integration examples) and call the desired tools in sequence to build or modify your presentation.

Prerequisites:\n- Python 3.10 or higher\n- uv (or pip) package manager\n- Microsoft PowerPoint installed for advanced features (Windows/macOS)\n\nOption 1 — Using uvx (Recommended for ephemeral use):\n1. Ensure uvx is installed on your system.\n2. Run the server directly with uvx from your client configuration:\n\nbash\nuvx --from office-powerpoint-mcp-server ppt_mcp_server\n\n\nOption 2 — Local installation (clone and install):\n1. Clone the repository:\nbash\ngit clone https://github.com/ihatesea69/Office-PowerPoint-MCP.git\ncd Office-PowerPoint-MCP\n\n2. Install dependencies:\nbash\npip install -r requirements.txt\n\n3. Run or integrate the server using your MCP client configuration (e.g., via uvx as shown in Option 1).

Tips and common considerations:\n- Environment variable MCP_DEBUG=1 enables verbose logging to help diagnose integration issues.\n- When inserting media or templates, prefer absolute file paths to avoid path resolution problems across different environments.\n- Ensure the Python environment used to run the server has read/write access to the target directories where presentations will be created or stored.\n- If a template or theme isn’t found, use list_available_presentations or list to inspect available resources, and verify paths.\n- For production deployments, consider containerizing the service and enforcing proper access controls to prevent unauthorized modifications to slide content.