This page adapts the HeyGen Manus MCP guide pattern for DeckFlow. The final Manus integration path depends on whether DeckFlow appears as a first-party Manus tool or is added through a custom MCP endpoint.
Prerequisites
- A Manus account with agent access.
- A DeckFlow account with MCP access.
- A DeckFlow API key, unless the Manus integration stores it through a managed connector.
- A confirmed DeckFlow integration path in Manus.
- Permission to upload or reference source files used by the agent.
Connect DeckFlow
Connection path is TBD for Manus-specific UI, but the confirmed DeckFlow MCP endpoint is:
https://dev.deckflow.com/mcp/v1/
If DeckFlow is available as a built-in Manus tool:
- Open Manus.
- Go to Connect Your Tools.
- Search for
DeckFlow. - Click Connect.
- Configure the DeckFlow API key if the managed connector asks for one.
If Manus requires a custom MCP endpoint:
- Open the Manus tool or integration settings.
- Add a custom MCP server named
DeckFlow. - Set the endpoint to
https://dev.deckflow.com/mcp/v1/. - Configure the DeckFlow API key using the supported Manus secret or connector flow.
Use DeckFlow In A Manus Agent
Open the agent workspace and select the DeckFlow tools for the agent. Then write a natural-language task describing the desired workflow.
Example prompt:
Every Monday morning, collect the latest product notes from the workspace,
use DeckFlow to create a concise internal update deck, export PPTX and PDF,
and send me the temporary download links.
Manus should orchestrate source collection, submit the DeckFlow task, monitor progress, and deliver the result package.
Scheduled Or Unattended Workflows
Manus-style agents are useful for recurring DeckFlow tasks:
- Generate weekly status decks from notes or reports.
- Translate sales decks for regional teams.
- Revamp old decks using the latest Brand DNA.
- Compress delivery packages before sending to customers.
- Extract PPTX text or font usage for audit workflows.
The final docs should state whether DeckFlow MCP allows unattended execution and how API key scope, file retention, and billing work for scheduled agents.
Recommended Agent Instructions
Before using DeckFlow, confirm the workflow type, input files, output
format, and target workspace. For scheduled jobs, report task IDs,
warnings, output links, and any failed files.
Parameters To Confirm
| Parameter | Question |
|---|---|
| Manus path | Is DeckFlow a built-in Manus tool, custom MCP connector, or both? |
| API key transport | How does Manus store and send the DeckFlow API key? |
| Scheduled jobs | Are recurring/unattended tasks supported by DeckFlow policy? |
| Output delivery | Temporary download links are confirmed. Should Manus attach files or save outputs to a DeckFlow workspace too? |