cursorrules

A set of operating rules for an MCP server that controls a live PowerPoint desktop application on Windows.

In plain words
What is it for?
Use it when opening, creating, editing, exporting, or closing PowerPoint presentations through the server's presentation, slide, shape, text, table, chart, and image tools.
Why use it?
It prevents editing mistakes by requiring a presentation session, consistent identifiers, correct indexing, and an explicit save when closing.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/sbroenne/mcp-server-powerpoint/cursorrules
Clone the repo
git clone --depth 1 https://github.com/sbroenne/mcp-server-powerpoint

Made for: Cursor.

Per session 785 This file is loaded in full into every session.
When invoked 785 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00785 $0.00785
Opus 5 $0.00392 $0.00392
Sonnet 5 $0.00157 $0.00157
Haiku 4.5 $0.00078 $0.00078

Measured 2d ago against content hash ff490ae5071a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/.cursorrules · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

.cursorrules — PowerPoint MCP Server Skills

You are assisting with mcp-server-powerpoint, a Windows-only MCP server that drives a live PowerPoint desktop instance via COM. When using the PowerPoint MCP tools (not when editing this repo's C# source), follow these rules:

Session Rules

  • Call presentation(action: "open", filePath: ...) before any editing tool; use the returned sessionId for every subsequent call.
  • presentation(action: "create", ...) creates a file and leaves its session open.
  • Close with save: true to persist changes.
  • presentation(action: "close", ...) returns immediately; it does not wait for the PowerPoint process to fully exit. Do not poll for process exit.

Tool Shapes

  • Session lifecycle, templates, and document properties use the presentation action-dispatch tool with camelCase arguments.
  • Domain tools (slide, shape, textframe, table, chart, image, notes, layout, master, animation, export) are action-dispatch: call as tool(action: "kebab-action", session_id: ..., snake_case_param: ...).

Indexing Rules

  • slide_index, shape_index, and table row/column are all 1-based. The first slide is slide_index=1, not 0.

Verification Rules

  • After adding or repositioning any shape, table, chart, or image, call export(action: "export-slide-to-image", session_id: ..., slide_index: ..., output_path: ...) and inspect the result before moving on or saving. Do not treat success: true from a mutation call as proof the slide looks right.
  • For a finished multi-slide deck, call export(action: "export-all-slides-to-images", ...) once as a final pass.

Behavioral Rules

  • Never ask the user clarifying questions you can answer yourself — use list_sessions, slide(action: "get-count", ...), shape(action: "get-count", ...), textframe(action: "get-text", ...), layout(action: "get-layout", ...), master(action: "get-title-font"/ "get-body-font"/"get-background-color", ...), table(action: "get-cell-text", ...), chart(action: "get-chart-data", ...), notes(action: "get-notes-text", ...) to discover current state.
  • Always finish a task with a plain-text summary (file path, slide count, what changed). Never end a turn with only a tool call.
  • Prefer targeted updates (table(action: "set-cell-text", ...), shape(action: "set-position", ...), shape(action: "set-size", ...)) over delete-and-recreate for small changes.
  • chart(action: "add-chart", ...) supports exactly one data series per call — there is no multi-series parameter.
  • There is no slide-reorder tool — plan the final slide order before calling slide(action: "add-blank", ...).

Read the full file on GitHub · 61 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 61 lines · 785 tokens per session scan A ff490ae5071a

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository sbroenne/mcp-server-powerpoint (19 stars, last pushed 2d ago), licensed MIT. It adds 785 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.