Claude PowerPoint MCP: native, editable slides in claude.ai, Desktop, and Claude Code

Updated 2026-08-11 · ~5 min read · Guide

The SlideForge connector in the Claude connector directory gives Claude a real PowerPoint engine over MCP: ask for a slide or a deck and get back a native, editable .pptx in about a second — real text boxes and chart shapes, not a picture of a slide — with your numbers bound verbatim and a per-field fidelity report. Setup is one click plus one setting almost everyone misses, covered below.

TL;DR

  • Connect: claude.ai → Connectors → search SlideForge → Connect (OAuth, auto-creates an account with 60 free slides).
  • Then set Tool access to “Tools already loaded” — with Claude's default, Claude often builds slides with its own code tools and never calls the connector.
  • 200+ layout patterns, rendered deterministically in under a second — no model in the render path, so the same request produces the same slide.
  • Verifiable output: every render reports, field by field, whether your content was bound verbatim. A defective slide is never billed.
  • $0.05 per slide, no subscription. PDF/image→editable-pptx conversion and 35-language translation ride the same connector.

Connect it (three surfaces, one account)

claude.ai and Claude Desktop — install from the directory: open claude.ai/directory/connectors/slideforge (or Settings → Connectors → search SlideForge), click Connect, and complete the sign-in. The connector follows your Claude account across web, Desktop, and mobile.

Any MCP client, manually — add a custom connector with the URL:

https://api.slideforge.dev/mcp/

Claude Code (terminal) — one command, covered step by step in the Claude Code MCP guide.

The setting that makes Claude actually use it

Symptom:SlideForge is connected, you ask for a PowerPoint — and Claude starts writing python-pptx code with its built-in skills instead of calling the connector. The connector looks broken. It isn't.

Cause: Claude's default Tool access mode, “Load tools when needed”, keeps connector tools out of context until Claude decides to fetch them — and for slides it usually reaches for its own built-in approach first.

Fix (once, global): open the tools menu in the chat input → Connectors → SlideForge → Tool access → “Tools already loaded”. From then on Claude sees the SlideForge tools in every conversation and uses them when you ask for slides.

If you tell Claude explicitly “use SlideForge” it will also load the tools on demand — the setting just removes the need to say it every time.

Generate your first slide

Make a KPI dashboard slide for our Q3 board update:
ARR $4.2M, up 18% QoQ. Net revenue retention 112%.
Logo churn 1.4%. Cash runway 19 months.

Claude picks a form from the catalog, calls create_slide, and the result card shows an inline preview with a download link for the .pptx. Open it and click on $4.2M — the cursor lands in an editable text box. Decks work the same way: describe the slides, or paste the data, and create_deck renders them in parallel into one file.

Connector vs. Claude's built-in PowerPoint skill

Claude can produce .pptx files on its own by writing python-pptx code, and for a quick one-off with no signup that is genuinely fine. The differences show up when the deck has to be right:

  • Time: generated code takes minutes per deck; a typed intent renders in under a second, decks in parallel.
  • Numbers: in generated code your figures pass through the model on the way to the slide. The connector binds supplied values verbatim and reports it per field — fabrication on the render path is structurally impossible.
  • Layout: freshly generated layout code varies run to run; the connector composes from 200+ maintained patterns with overflow and fit validation.
  • Repeatability: the same intent renders the same slide — which is what makes weekly reports and CI-produced decks diffable.

The honest converse: if you need a bespoke layout outside any catalog, generated python-pptx is exactly the right escape hatch — and the connector exposes it too, as mode=code with theme, widgets, and a geometry linter included.

Frequently asked questions

Can Claude make me a PowerPoint?

Yes, two ways. Out of the box, Claude can write python-pptx code and produce a .pptx file itself — workable for a one-off, but each deck is freshly generated code: minutes rather than seconds, layout quality varies, and nothing checks the output. With the SlideForge connector, Claude sends a typed slide intent to a deterministic rendering engine and gets back a finished, editable .pptx in about a second, with your numbers bound verbatim and a per-field fidelity report.

Why does Claude ignore the connector and write python-pptx code instead?

Because of a default setting. Claude's default Tool access mode, "Load tools when needed", keeps connector tools out of context — so when you ask for a slide, Claude reaches for its built-in code skills instead of SlideForge. Fix: open the tools menu in the chat input → Connectors → SlideForge → Tool access → "Tools already loaded". The setting is global and only needs to be set once. This is the single most common reason a connected SlideForge appears to do nothing.

How do I connect Claude to PowerPoint?

Claude doesn't connect to the PowerPoint application — it generates PowerPoint files. Install the SlideForge connector from the Claude directory (claude.ai/directory/connectors/slideforge), sign in with the OAuth prompt, and ask for a slide or deck. You download a native .pptx that opens in PowerPoint, Google Slides, or Keynote with every text box and shape editable.

Does it work in Claude Desktop and on mobile?

Yes. A connector installed from the directory follows your Claude account — claude.ai in the browser, Claude Desktop, and Claude mobile all see it. Claude Code (the terminal agent) connects separately with one command; see the Claude Code guide.

Is the output really editable, or is it an image of a slide?

Native PowerPoint objects: text is text, tables are tables, charts are chart shapes. Open the file and click a number — the cursor lands in a text box. Several slide tools export a screenshot inside a .pptx wrapper, which looks identical until someone tries to edit it. That test takes ten seconds and settles it.

Can Claude turn a PDF or a screenshot of a slide into editable PowerPoint?

Yes. Upload the file in the conversation and ask for it as editable PowerPoint — SlideForge's upload_asset tool takes PDFs and slide images and reconstructs supported layouts as real text frames and shapes, with a free analysis first that tells you what the result will look like before you spend anything.

What does it cost?

$0.05 per slide, on every path — no subscription, no download quota. Signup through the OAuth flow is automatic and starts with 60 free slides, no credit card. A slide with a blocking defect is never billed, and re-requesting an identical input is free.

Connect SlideForge to Claude

One click in the directory, 60 free slides, no card. The first slide takes under a minute.

Open in ClaudeMCP docs