PowerPoint Automation MCP Server for Claude Desktop

Created By
socamaloa year ago
Overview

what is PPT_MCP_Server?

PPT_MCP_Server is a PowerPoint automation server designed to work with Claude Desktop via the Model Control Protocol (MCP). It enables users to automate tasks in Microsoft PowerPoint, such as creating presentations, adding slides, and modifying content.

how to use PPT_MCP_Server?

To use PPT_MCP_Server, clone the repository, install the necessary dependencies, and configure Claude Desktop to connect to the MCP server. Once set up, you can issue commands to control PowerPoint through Claude Desktop.

key features of PPT_MCP_Server?

  • Create, open, save, and close PowerPoint presentations
  • List all open presentations
  • Get slide information and content
  • Add new slides with various layouts
  • Update text content in shapes
  • Set slide titles
  • And more!

use cases of PPT_MCP_Server?

  1. Automating the creation of PowerPoint presentations for meetings.
  2. Quickly modifying existing presentations by adding or updating slides.
  3. Streamlining the process of generating reports and presentations from data.

FAQ from PPT_MCP_Server?

  • What operating system is required to run PPT_MCP_Server?

PPT_MCP_Server works only on Windows with Microsoft PowerPoint installed.

  • Do I need to install any additional software?

Yes, you need Python 3.7+ and the pywin32 and fastmcp packages.

  • Can I use this server without Claude Desktop?

No, this server is specifically designed to work with Claude Desktop.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
socamalo
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago