Build presentation workflows with DeckFlow.
Create, revamp, translate, convert, render, and inspect decks through API and CLI.
# Connect DeckFlow to an AI agent
claude mcp add --transport http \
deckflow https://dev.deckflow.com/mcp/v1/What you can build
Three product pillars and a stack of single-purpose deck tools — all reachable from the same workspace credit balance.
Create
Generate decks from documents, URLs, and plain text — formulas, charts, and diagrams kept at the structural level.
Explore→Revamp
Restyle PPTX, Keynote, and PDF with professional templates or your Brand DNA — the content stays untouched.
Explore→Translate
Translate decks across 30+ languages with layout, fonts, and animations kept intact.
Explore→HTML → PPTX
Turn rendered HTML — pages, charts, components — into editable PPTX, not flattened screenshots.
Explore→PPTX → any
Export PowerPoint as PDF, image, video, or modernized PPTX. Layout and animations preserved.
Explore→Keynote → any
Open Keynote everywhere — export to HTML, PDF, or image with the original visuals intact.
Explore→PDF → Markdown
Extract PDF content into structured Markdown — headings, lists, and tables preserved for downstream AI workflows.
Explore→More deck APIs
23 single-purpose utilities across four categories: conversion, extraction, merge/split, and optimization.
Explore→Three ways to integrate
Pick the surface that fits how you work — a REST API for your backend, an MCP server for AI agents, or a CLI for the terminal and CI.
REST API
Server-side automation
- Authenticate with an API key tied to your workspace
- Submit a task, poll for status, download the result
- Same-format output — a PPTX returns a PPTX
MCP server
For AI agents
- Let agents call DeckFlow directly from chat or code
- Works with Claude Code, Claude Web & Desktop, Manus, and OpenAI
- Agents use your workspace — no keys pasted into chat
claude mcp add --transport http \
deckflow https://dev.deckflow.com/mcp/v1/CLI
Terminal & CI
- DeckOps runs cloud tasks from your shell
- DeckUse edits PPTX locally — no credentials
- Scriptable for CI and automated pipelines
npm install -g deckuse # local edits
npm install -g deckops # cloud tasksPricing
Free to try, paid plans from $9 per month. The API, MCP server, and CLI are available on every paid plan — no separate developer tier.
Free
30 Credit + 3 Spark / month
Try the API, MCP server, and CLI end to end before committing.
Start freeStarter
1,200 Credit + 120 Spark / year
For individual creators automating their own deck workflow.
Start freePro
6,000 Credit + 600 Spark / year
For teams running deck workflows at scale.
Start freeAll plans include the same API, MCP, and CLI surfaces — usage draws from your workspace credits. View full pricing →
Start building
Two steps from idea to your first call.
What you can count on
30+ languages
EN↔ZH, JA, ES, DE optimized; layout preserved on every pair.
Up to 500 MB / file
PPTX, Keynote, PDF, Word — no manual splitting.
Agent-ready via MCP
Claude Code, Claude Web & Desktop, Manus, OpenAI.
Encrypted & deleted
Files encrypted in transit. Removed automatically when tasks finish.
Frequently asked questions
Create a key in your workspace settings and include it with each request. The key is tied to the workspace where you created it, and its usage draws from that workspace's credits.
No. API, MCP, and CLI access is included with paid plans rather than sold as a standalone tier, and usage draws from your plan's credits.
Claude Code, Claude Web and Desktop, Manus, and OpenAI-compatible hosts. Point them at https://dev.deckflow.com/mcp/v1/ and connect your workspace.
PPTX, Keynote, PDF, Word, and Excel, depending on the operation. The API returns the same format you send in, so a PPTX stays a PPTX and a Keynote stays a Keynote.
No. The MCP server lets an agent call DeckFlow through your connected workspace, so keys never get pasted into a chat. Usage still draws from your workspace quota.
Three paths, same workspace. Use the REST API for server-side automation, the MCP server when an AI agent needs to call DeckFlow from chat or code, and the CLI (DeckOps for cloud tasks, DeckUse for local PPTX edits) for terminals and CI. Pick whichever fits the environment you already work in.
The Free plan includes 30 Credit + 3 Spark every month — enough to try the REST API, MCP server, and CLI end to end. Paid plans start at $9 per month (billed annually) for higher allotments.