Kadal Deck

What Kadal Deck does

Kadal Deck MCP server connects AI agents to the Kadal Deck slide-deck format and workflow. It helps an agent move from a talk idea to a structured MDX presentation by outlining the talk, writing slides, checking the result, rendering slides, and applying corrections.

A Kadal Deck presentation is authored in one deck.mdx file. The file uses Markdown and MDX, with slides separated by --- and components available for interactive content. The MCP workflow is therefore suited to agents that need to create or modify source files while respecting the deck's structure.

The project also provides a hosted MCP server for published decks. That option lets supported AI clients work with presentations that have already been published through Kadal Deck.

How it works

The MCP server teaches an AI client how the Kadal Deck format is organized and exposes operations for the main authoring loop:

• Create an outline for a presentation.
• Write or revise slides in MDX.
• Lint the deck to check its contents.
• Render slides so the agent can inspect its output.
• Correct problems found during review.

Rendering supports an iterative process rather than stopping after text generation. An agent can produce a deck, inspect the rendered result, and make another pass based on what it sees. The same deck can then be opened in Kadal Deck for editing, rehearsal, presentation, and audience participation.

Tools and capabilities

The MCP workflow supports the following capabilities:

• Talk and slide outlining.
• MDX slide creation and revision.
• Deck linting.
• Slide rendering for review.
• Fixing issues after inspection.
• Working with published decks through the hosted MCP server.

Kadal Deck itself supports presenter notes, themes, interactive polls, quizzes, word clouds, Q&A, reactions, and other deck components. Those presentation features are authored in the deck format; the MCP server's documented agent workflow focuses on outlining, writing, checking, rendering, and fixing decks.

Setup and configuration

Kadal Deck projects require Node.js 20.19 or later. A project can be created with the Kadal Deck package, installed with npm, and started locally for browser-based editing. The resulting project contains a deck.mdx file that an agent can work on through an MCP-compatible client.

The MCP server is intended for use from AI clients including Claude Code, Cursor, and VS Code. The hosted MCP option can expose published decks to Claude, ChatGPT, and Cursor. Kadal Deck also has a browser builder with its own AI assistant; that assistant uses a provider key from OpenAI, Anthropic, Google, or OpenRouter, which is separate from the agent-facing MCP workflow described here.

Limitations and notes

The agent works with Kadal Deck's MDX representation, so it is most appropriate when the target output is a Kadal Deck presentation rather than PowerPoint, Google Slides, or a generic Markdown document. Visual review depends on rendering the deck and examining the result; generated slide text alone is not the complete presentation experience.

The broader Kadal Deck project can present built decks offline and export them to PDF, PNG, and PPTX. Live rooms, audience interaction, rehearsal tools, and hosting are part of Kadal Deck itself and should not be treated as additional MCP tools unless they are represented in the deck workflow.