DeckFlow MCP is intended for AI agents that need to create, revamp, translate, convert, extract, merge, split, or optimize presentation and office files without asking the user to switch tools manually.
The content below follows the structure of heygen-docs/mcp/, while using the currently confirmed DeckFlow MCP endpoint, API key-only authentication, first-batch client list, and temporary download-link output behavior. Anything not yet confirmed is marked as TBD.
Endpoint
https://dev.deckflow.com/mcp/v1/DeckFlow MCP uses API key authentication only. The exact API key header, secret field, environment variable, and key creation URL still need confirmation before setup pages become implementation-ready.
What You Can Do
Once connected, an AI agent should be able to call DeckFlow workflows in three major groups:
Product Workflows
| Capability | Description |
|---|---|
| Create | Generate a deck from PDF, Word, Markdown, URL, plain text, research material, or a topic prompt. Output can be PPTX, PDF, HTML, or image, depending on final API support. |
| Revamp | Redesign an existing PPTX, Keynote, or PDF deck while preserving original text, data, and structure. Supports professional templates or Brand DNA when available. |
| Translate | Translate decks and office documents while preserving layout. Target use cases include PPTX, Keynote, PDF, Word, and Excel files with glossary and language controls. |
File Tools
| Category | Description |
|---|---|
| File Converter | Convert HTML, Keynote, Markdown, PDF, PowerPoint, Word, and images into delivery-friendly formats such as PPTX, PDF, PNG, WebP, HTML, or MP4. |
| Extractor | Extract OCR text, PPTX font usage, or PPTX text shapes for review, migration, and automation workflows. |
| Merger & Splitter | Merge PPTX decks, split PPTX files by slide, or build an HTML player package from multiple HTML files. |
| Optimizer | Compress files and videos, resize images, or embed fonts into PPTX files before delivery. |
Task Management
DeckFlow workflows are likely asynchronous because most operations involve uploaded files, rendering, conversion, or AI processing. The MCP surface should therefore include a consistent task model:
| Capability | Description |
|---|---|
| Submit task | Start a Create, Revamp, Translate, conversion, extraction, merge, split, or optimization job. |
| Check status | Poll task status, progress, warnings, and failure details. |
| Fetch result | Return generated files, previews, metadata, and temporary download links. |
| Cancel task | Stop a queued or running task when supported. |
Supported MCP Clients
DeckFlow MCP should work with the confirmed first-batch clients below. Other MCP-compatible clients can be documented after support is confirmed.
Launch setup drafts now exist for these agent/client pages:
| Client | Suggested Page |
|---|---|
| Claude Code | claude-code.md |
| Claude Web / Desktop | claude-web.md |
| Manus | manus.md |
| OpenAI / ChatGPT | open-ai.md |
How It Works
- Connect the MCP client to the DeckFlow MCP endpoint.
- Authenticate with DeckFlow using an API key.
- Give the agent a natural-language task and attach or reference the needed source files.
- The agent selects the appropriate DeckFlow MCP tool and submits a task.
- DeckFlow processes the task asynchronously.
- The agent checks status and returns final files, previews, metadata, or temporary download links.
Remote MCP Draft
| Remote MCP | |
|---|---|
| Setup | Add https://dev.deckflow.com/mcp/v1/ to an MCP-compatible client. |
| Runs on | DeckFlow hosted infrastructure. |
| Authentication | API key only. |
| Billing | TBD: plan credits, per-task credits, API billing, or included usage. |
| File handling | TBD for input upload. Completed outputs return temporary download links. |
| Best for | Confirmed launch agents: Claude Code, Claude Web/Desktop, Manus, and OpenAI/ChatGPT. |
Source Basis
This MCP draft is based on:
deckflow-key-features.md: Create, Revamp, and Translate product workflows.deckflow-tools-summary.md: 23 browser tools across File Converter, Extractor, Merger & Splitter, and Optimizer.heygen-docs/mcp/: Reference structure for overview, setup, supported clients, tools, and examples.
Parameters Still Needed
The following decisions must be defined before MCP docs can become implementation-ready:
| Area | Missing Definition |
|---|---|
| Endpoint | Production vs. dev/staging semantics, regional URLs if any, versioning policy, and trailing slash policy. |
| Authentication | API key creation URL, header/secret field name, token lifetime, rotation, account/workspace scope, and reconnect behavior. |
| File input | Upload mechanism, supported source URL rules, maximum files per task, file retention, and attachment behavior per MCP client. |
| Task lifecycle | Status enum, progress fields, cancellation support, timeout behavior, retries, and result expiration. |
| Tool schemas | Final MCP tool names, required parameters, optional parameters, enums, defaults, and validation rules. |
| Output delivery | Temporary download URL format, preview format, metadata, signed URL lifetime, and whether outputs are also persisted in a DeckFlow workspace. |
| Limits | File size, page count, slide count, batch count, rate limits, concurrency limits, and plan restrictions. |
| Billing | Credit model, free tier behavior, failed task charges, and usage visibility. |
See parameter-checklist.md for the full checklist.
See confirmation-questions.md for the direct questions that need product/API owner answers.