SlideForge MCP Server

Deterministic, fully editable PowerPoint from typed slide intents. 150+ layouts, brand templates. That is what the slideforge mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Remote MCP server + REST API. No local install, no Python environment, no python-pptx boilerplate. OAuth 2.1 for Claude Desktop & ChatGPT; API key for everything else.

• Native, editable .pptx. — Real shapes and text boxes — not images, not HTML exports. Openable and editable in PowerPoint
• Your template, natively. — Upload your company's .pptx — slides are built ON your file (theme, masters, fonts), not a color-matched imitation
• 97% quality parity with Gamma — in our own blind side-by-side benchmark (internal instrument, not third-party)

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 7 tools. What each one is for:

• create_slide — ONE slide from a structured intent (form + typed fields) or a brief; mode=safe validates-then-renders in one call; mode=code for sandboxed
• create_deck — Whole deck: slides[] of intents (code-mode slides are first-class children), parallel render, one merged .pptx, per-slide fidelity rollup + per-slide
• plan_slide — Brief → top form/variant candidates with confidence
• browse_catalog — 150+ patterns with per-form JSON Schemas + copy-pasteable example intents, themes, the code-mode widget toolkit. Pass an uploaded theme_id to list
• translate_deck — Translate any PPTX preserving formatting (32 languages)
• upload_asset — Logos, theme PPTX, images; purpose=pdf extracts a PDF into editable slide intents; or AI-generate an image. Theme upload (purpose=theme, base64 data)
• manage_account — Balance, usage, jobs, security status, feedback

What it needs from you

Configuration is passed through the environment: SLIDEFORGE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. SlideForge's toolset — create_slide, create_deck, plan_slide and 4 more — is a fair guide to whether it matches your workflow. It is maintained by dev.slideforge; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.