Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Create, edit, and export presentations with AI. Requires desktop Microsoft PowerPoint on Windows.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"powerpoint": {
"command": "npx",
"args": [
"-y",
"@sbroenne/mcp-server-powerpoint"
]
}
}
}在终端中运行这条命令
claude mcp add powerpoint -- npx -y @sbroenne/mcp-server-powerpoint粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"powerpoint": {
"command": "npx",
"args": [
"-y",
"@sbroenne/mcp-server-powerpoint"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"powerpoint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sbroenne/mcp-server-powerpoint"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 sbroenne 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.3.4)于14天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 .NET, Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, OpenTakeoff
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Create and edit real PowerPoint presentations with AI assistants or scripts. Build a new deck or update an existing .pptx file. Add slides, format text and shapes, create charts and tables, insert images, and write speaker notes using the installed Microsoft PowerPoint desktop application on Windows.
Choose how you work. Connect your AI assistant through the Model Context Protocol server, use the VS Code extension with GitHub Copilot Chat, or run pptcli from terminal commands and scripts. The packages require desktop PowerPoint; they do not replace it.
Review the actual result. The MCP server can export presentations to PDF or render slides as images through PowerPoint. An assistant that can inspect images can then check for overlapping shapes, text overflow, and layout problems before you share the presentation.
Technical Requirements:
[!TIP]
Also automating spreadsheets? Check out Excel MCP Server —
the sister project, built the same way.
32 MCP tools with 215 operations across 17 domains:
The tool total includes 15 read-only aliases; the operation total counts each unique action once.
.potx/.pptx template's masters/theme/layouts, read the current theme name, set/read PowerPoint's advisory Mark as Final flag, read/write built-in and custom document properties, and manage string tagsEvery domain is exposed as a single action-dispatch tool (e.g. shape, table, chart, presentation) with an action parameter selecting the specific operation — keeping the tool list small for AI assistants while still exposing every operation.
📚 [Complete Feature Reference →](https://powerpointmcpserver.dev/features/) — detailed documentation of every tool and operation
Build a deck from scratch:
Tables & charts:
Formatting & shapes:
Speaker notes:
Templates & themes:
Visual verification:
Perfect for:
.pptx decksNot suitable for:
| Platform | Installation |
|---|---|
| VS Code | Install Extension (one-click, recommended) |
| Claude Desktop | Download .mcpb from latest release (requires Node.js 18+) |
| Any MCP Client | Run npx -y @sbroenne/mcp-server-powerpoint@latest |
| Details | 📖 Full Installation Guide → |
⚠️ Important: Close any open instances of the target file before automating it — the server needs exclusive access to the presentation while it's driving PowerPoint.
This project provides both a CLI and an MCP Server interface. Choose based on your use case:
| Interface | Best For | Why |
|---|---|---|
CLI (pptcli / powerpointcli.exe) | Coding agents (Copilot, Cursor, Windsurf) + scripting | Single tool, no large schemas — better for cost-sensitive, high-throughput automation. |
MCP Server (mcp-powerpoint) | Conversational AI (Claude Desktop, VS Code Chat) | Rich tool discovery, persistent session. Better for interactive, exploratory workflows. |
Manual installation:
# Primary: npm launchers select the matching native x64 or ARM64 Windows runtime
npx -y @sbroenne/mcp-server-powerpoint@latest npx -y @sbroenne/pptcli@latest --help
dotnet tool install --global Sbroenne.PowerPointMcp.McpServer dotnet tool install --global Sbroenne.PowerPointMcp.CLI
npx add-mcp "mcp-powerpoint" --name powerpoint-mcp
# Optional: Install the agent skill for better AI guidance
npx skills add sbroenne/mcp-server-powerpoint --skill powerpoint-mcp
💡 The VS Code extension installs this skill automatically. Manual
npx skills addis for other
MCP clients (Claude Code, Cursor, Windsurf, etc.).
PowerPointMcp uses Windows COM automation to control the actual PowerPoint application (not just `.pptx` files).
The MCP Server and CLI are two equal, first-class entry points. Each hosts its own PowerPointMcp Service that manages presentation sessions — the MCP Server runs it in-process (direct calls, no pipe), while the CLI uses a background daemon over a named pipe so sessions persist across CLI invocations:
┌──────────────────────┐ ┌──────────────────────┐
│ MCP Server │ │ CLI (pptcli) │ │ (AI assistants) │ │ (coding agents) │ └──────────┬───────────┘ └──────────┬───────────┘ │ in-process │ named pipe → │ (direct calls) │ background daemon ▼ ▼ ┌──────────────────────┐ ┌──────────────────────┐ │ PowerPointMcp │ │ PowerPointMcp │ │ Service │ │ Service │ │ (session mgmt) │ │ (daemon; sessions │ │ │ │ persist across │ │ │ │ CLI invocations) │ └──────────┬───────────┘ └──────────┬───────────┘ ▼ ▼ Core Commands Core Commands ▼ ▼ ┌──────────────────────┐ ┌──────────────────────┐ │ PowerPoint COM API │ │ PowerPoint COM API │ │ (PowerPoint. │ │ (PowerPoint. │ │ Application) │ │ Application) │ └──────────────────────┘ └──────────────────────┘
Both entry points share the same Core Commands codebase, so every operation behaves identically. They are separate processes, though: each runs its own PowerPointMcp Service and its own PowerPoint instance, and they do not share live sessions with each other.
Key Benefits:
pptcli calls, so scripts don't re-open files each timePowerPoint.Application via COM, not just file parsingBootstrapped from exact authenticated stargazer timestamps, then updated daily from GitHub's exact public star count. Only date/count aggregates are retained.
📚 [MCP Server Guide →](src/PowerPointMcp.McpServer/README.md) | [CLI Guide →](src/PowerPointMcp.CLI/README.md) | [Agent Skills →](skills/README.md)
📖 [Complete Feature Reference](https://powerpointmcpserver.dev/features/) • [Installation Guide](https://powerpointmcpserver.dev/installation/) • [Changelog](https://powerpointmcpserver.dev/changelog/) • [Native Feature Roadmap](docs/POWERPOINT-NATIVE-FEATURE-AUDIT.md) • [Contributing](https://powerpointmcpserver.dev/contributing/) • [Security](https://powerpointmcpserver.dev/security/) • [Privacy](https://powerpointmcpserver.dev/privacy/)
License: MIT
只显示了开头部分;其余内容请在仓库中阅读