Use this guide when the user wants DeckFlow available inside Claude Code projects. This page follows the same structure as the HeyGen Claude Code MCP guide, with DeckFlow-specific API key transport details still to confirm.
Prerequisites
- Claude Code installed.
- Node.js installed, if required by the active Claude Code MCP resolution path.
- A DeckFlow account with MCP access.
- A DeckFlow API key.
- Permission to upload or reference files used in DeckFlow workflows.
Add The MCP Server
Run this command in your terminal, outside the Claude Code interactive session:
claude mcp add --transport http deckflow https://dev.deckflow.com/mcp/v1/
To make DeckFlow available across all Claude Code projects, add the user scope flag:
claude mcp add --transport http -s user deckflow https://dev.deckflow.com/mcp/v1/
Alternative: Direct Config Edit
If the target Claude Code version supports direct config editing, add DeckFlow to ~/.claude.json:
{
"mcpServers": {
"deckflow": {
"type": "http",
"url": "https://dev.deckflow.com/mcp/v1/"
}
}
}
Restart Claude Code after editing the config file.
Authentication
DeckFlow MCP uses API key authentication only.
The final docs still need to define how Claude Code should pass the API key to the remote MCP server. Possible patterns include client secret configuration, HTTP header configuration, or an MCP auth prompt.
The user can run the MCP status view inside Claude Code:
/mcp
This page still needs the final credential storage instructions, API key creation URL, and environment variable or header name.
Verify The Connection
After setup, confirm the server is active:
claude mcp list
Or from inside Claude Code:
/mcp
The user should see deckflow listed with a connected status and available tools.
Usage
Example prompt:
Use DeckFlow to turn this research PDF into a 10-slide PPTX deck,
then tell me when the generated file is ready.
Claude Code should call the appropriate DeckFlow MCP tool, poll the task, and return the generated file as a temporary download link.
Recommended Agent Instructions
For better results, ask Claude Code to inspect DeckFlow capabilities before submitting file tasks:
Before using DeckFlow, call the available capability or account tool
to confirm supported input formats, output formats, file limits, and
whether Create, Revamp, Translate, and Tools are available.
Scoping
| Scope | Flag | Config Location | Availability |
|---|---|---|---|
| Local | none | .mcp.json in project directory | Current project only |
| User | -s user | ~/.claude.json | All projects for current user |
Parameters To Confirm
| Parameter | Question |
|---|---|
| API key creation | Where does the user create or copy the DeckFlow API key? |
| API key transport | Should Claude Code pass the key through a header, secret field, env var, or prompt? |
| Credential storage | What env var and config file should be documented? |
| Verification tool | Should docs recommend get_current_user, get_deckflow_capabilities, or another health check? |
| Output handling | Temporary download links are confirmed. Should outputs also be saved in a DeckFlow workspace? |