MCP Setup

This page is a setup draft. It mirrors the shape of the HeyGen MCP setup pages, while using the confirmed DeckFlow endpoint, API key-only auth model, first-batch clients, and temporary download-link output model.

Prerequisites

• A DeckFlow account.
• Access to the DeckFlow MCP beta or production integration.
• An MCP-compatible client that supports remote HTTP MCP servers.
• A DeckFlow API key.
• Permission to upload or reference source files used in Create, Revamp, Translate, and Tools workflows.

Endpoint

https://dev.deckflow.com/mcp/v1/

The docs currently use this endpoint exactly as provided. Confirm later whether this is the final production URL or a development endpoint.

Dedicated Client Guides

Use the dedicated pages for client-specific setup details:

This page remains the shared setup overview and fallback for generic MCP-compatible clients.

Authentication

DeckFlow MCP uses API key authentication only.

The final setup guide still needs the API key details:

Claude Code

Run the command from a terminal, outside the Claude Code interactive session:

claude mcp add --transport http deckflow https://dev.deckflow.com/mcp/v1/

To install it globally for all Claude Code projects:

claude mcp add --transport http -s user deckflow https://dev.deckflow.com/mcp/v1/

After adding the server, restart Claude Code or run the client-specific MCP refresh command if available.

Alternative Config

If direct config editing is supported in the target Claude Code version, the MCP server should look like this:

{
  "mcpServers": {
    "deckflow": {
      "type": "http",
      "url": "https://dev.deckflow.com/mcp/v1/"
    }
  }
}

Claude Web / Desktop

1. Open the connector or integration settings.
2. Add a custom connector named DeckFlow.
3. Set the remote MCP server URL to:

https://dev.deckflow.com/mcp/v1/

1. Save the connector.
2. Configure the DeckFlow API key using Claude's supported secret or connector flow.
3. Allow the DeckFlow tools when the client asks for tool permissions.

Other MCP Clients

The confirmed first-batch DeckFlow client list is Claude Code, Claude Web/Desktop, Manus, and OpenAI/ChatGPT. Other MCP-compatible clients can be documented later using the generic pattern below after product support is confirmed.

For clients that accept a JSON MCP server definition, use the same remote HTTP structure:

{
  "mcpServers": {
    "deckflow": {
      "type": "http",
      "url": "https://dev.deckflow.com/mcp/v1/"
    }
  }
}

If a client uses a different field name, map the final endpoint to its remote MCP URL field.

Verify The Connection

Use the MCP client's server list or tool discovery command to confirm:

• The deckflow server appears in the connected servers list.
• DeckFlow tools are visible.
• The client has access to a valid DeckFlow API key.
• A simple account or capability check succeeds, if DeckFlow provides one.

Suggested verification tool, if implemented:

get_current_user

or:

get_deckflow_capabilities

Both names are placeholders until the final tool schema is defined.

First Prompt

After setup, test with a low-risk task:

Use DeckFlow to list the available MCP capabilities and tell me which file formats are supported for Create, Revamp, Translate, and file conversion.

Then test a file workflow:

Use DeckFlow to convert this PowerPoint deck to PDF and return the temporary download link.

Client Permission Notes

MCP clients may ask for permission before each tool call. For smoother workflows, users can usually allow DeckFlow tools for the current chat, project, or workspace.

The final docs should explain permission scope carefully because DeckFlow tools can upload files, create derived files, and return downloadable outputs.

Setup Parameters To Define

For the direct product/API questions, see confirmation-questions.md.