This page adapts the HeyGen Claude Web MCP setup structure for DeckFlow. Final screenshots, API key transport, and plan requirements still need confirmation.
Prerequisites
- A Claude plan that supports custom connectors.
- A DeckFlow account with MCP access.
- A DeckFlow API key.
- Permission to upload or reference files in Claude.
Setup
1. Register The Connector
In Claude, navigate to the custom connector settings. The current HeyGen reference path is:
+ -> Connector -> Manage Connector -> + Add custom connectorSet the connector name to:
DeckFlowSet the remote MCP server URL to:
https://dev.deckflow.com/mcp/v1/2. Authenticate
After saving the connector, click Connect.
DeckFlow MCP uses API key authentication only.
Claude must support the required secret input flow, HTTP header configuration, or another approved way to send the DeckFlow API key to the remote MCP server. If Claude custom connectors cannot pass API keys securely, DeckFlow may need a first-party connector or an intermediate key exchange.
3. Configure Permissions
Claude may ask for permission before tool calls. For smoother workflows, users can allow DeckFlow tools for the current chat or connector, depending on Claude's permission model.
The final docs should explain that DeckFlow tools may upload files, create derived files, read task status, and return downloadable outputs.
Usage
Example prompt:
Use DeckFlow to translate this deck into Japanese while preserving
layout, then return the translated file.Claude should choose the matching DeckFlow MCP tool, submit the task, poll until complete, and return the result.
Suggested First Test
Use a low-risk capability discovery prompt:
Use DeckFlow MCP to list the supported workflows, input formats,
output formats, and file size limits available to this account.Limitations To Document
| Constraint | Detail To Confirm |
|---|---|
| Claude plan | Which Claude plans support custom MCP connectors at publish time? |
| DeckFlow plan | Which DeckFlow plans include MCP access? |
| API key setup | Where Claude users enter or store the DeckFlow API key. |
| File attachments | Whether Claude passes attached files directly to MCP or DeckFlow needs upload URLs. |
| Permission prompts | Whether users can set DeckFlow tools to always allow. |
| Output links | Temporary download links are confirmed; confirm signed URL lifetime. |
Parameters To Confirm
| Parameter | Question |
|---|---|
| Connector name | Should it be documented as DeckFlow, deckflow, or another display name? |
| API key transport | Can Claude custom connectors send the DeckFlow API key securely, and how should users configure it? |
| Screenshots | Do we have DeckFlow-specific Claude screenshots to include? |
| Plan requirements | What Claude and DeckFlow plans should be listed? |