kadal-deck
OfficialRelated Servers
Alternatives to kadal-deck
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceLocal-first MCP server & CLI for authoring Bento decks (single-file PPT) with AI agents and live browser preview. Enables programmatic creation, editing, validation, and presentation of Bento HTML decks.14 npm1MIT
- AlicenseAqualityBmaintenanceMCP server for Deckrun — generate presentation PDFs, narrated videos, and audio from Markdown. Built for AI agents and IDEs. Free tier: no API key required — generate PDFs instantly. Paid tier: set DECKRUN_API_KEY to unlock video, audio, and account tools.22MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to build an editable slide deck from a brief and local source documents over MCP — creating decks, adding sources, generating outlines and slides, reviewing and approving slides, checking figures against sources, and exporting to PPTX, PDF, HTML or Markdown. Everything stays local, with the same tools backing the bundled UI.MIT
- AlicenseNot gradedqualityBmaintenanceTurns an AI client into a slide author that produces single self-contained HTML decks with live diagrams, step-by-step reveals, in-place text editing and PDF export. It also lets the AI verify its own work through layout audits and screenshots, all locally with no API key.102 npmMIT

ToolsEnabled Slidesofficial
AlicenseNot gradedqualityBmaintenanceEnables building and editing real PowerPoint decks from any MCP host with a live local browser studio, slide locks, human-only pause/resume/undo/redo controls, and export to PPTX, PDF, or PNG. It preserves imported decks in one editable model while requiring no model calls, accounts, or API keys.MIT- FlicenseCqualityDmaintenanceA TypeScript-based MCP server that automatically generates structured technical presentation PPTX files via deck JSON and layout engine.9-
TDQS
Scored across 24 tools
Most tools have clearly distinct purposes: slide CRUD, deck setup, linting, rendering, preview, export, publishing, and sync/conflict handling are separable. A few pairs are adjacent (deck_check vs. deck_sync_status, deck_preview vs. slide_render, media_search vs. media_trending), but the long descriptions generally make the boundary clear enough for an agent.
All names are snake_case and use recognizable domain prefixes (deck_, slide_, media_, notes_), which makes the set readable. However, the convention mixes noun phrases (deck_conflicts, deck_outline, deck_frontmatter_schema) with verb phrases (deck_resolve, slide_add, media_search), and deck_read_slide is prefixed like a deck operation rather than a slide operation.
24 tools is on the heavy side and lands in the borderline 16–25 range. The domain genuinely needs many operations (authoring, media, validation, export, publishing, sync), but a few tools could conceivably be consolidated or made more composite without losing capability.
The surface covers the full deck lifecycle: scaffold, outline/read, slide CRUD and move, notes, deck frontmatter, media search/trending/attribution, linting, rendering, preview, build, export, publish, sync status, pull, conflict inspection, and conflict resolution. There are no obvious dead ends for the stated domain.