InstaDeck
Related Servers
Alternatives to InstaDeck
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude to build and modify slide decks with bullets, pictures, charts, tables, speaker notes, themes and transitions, then export them as PowerPoint pptx, PDF, per-slide images or outlines. It also reads and inspects existing presentations, finding and replacing content across whole folders, and can optionally open decks in the DeckCraft app for live editing.9Apache 2.0
- AlicenseNot gradedqualityDmaintenanceCreates AI-powered slide decks directly from Claude Desktop with live progress and QA scores.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and edit presentation decks—manipulating documents, slides, shapes, text, animations, transitions, and exports—while reading tabular data and generating 18 types of business charts.1MIT
- AlicenseAqualityCmaintenanceEnables turning a Markdown brief into a reviewed slide plan and then consistent, on-brand slide visuals via Claude Code, with human approval gates before any paid image generation.101MIT
- FlicenseAqualityCmaintenanceEnables Claude Code to create and edit presentation-grade visualizations such as cloud architecture diagrams, charts, KPI dashboards, and poster infographics, with auto-layout, themes, and export to SVG, PNG, JPG, and PDF.6-
- AlicenseNot gradedqualityCmaintenanceCreate designed Figma Slides by chatting with GitHub Copilot or Claude. It generates polished, multi-layout decks with 31 layouts and 17 design systems directly in Figma.MIT
TDQS
Scored across 20 tools
Most tools have clearly distinct purposes across assets, brand kits, decks, and history. Minor overlap exists between get_deck and get_deck_view (the latter explicitly says you never need it), and between validate_deck and the built-in validation reported by create_deck, but the descriptions do clarify these.
Every tool follows a predictable snake_case verb_noun pattern: get_design_guide, add_asset, create_brand_kit, list_decks, apply_ops, render_preview, etc. The convention is uniform across all 20 tools with no mixed casing or vague verbs.
20 tools is on the heavier side but the server spans several subdomains (assets, brand kits, decks, revision history), so most tools earn their place. A few (get_deck_view, extract_brand_colors) could arguably be folded in, but overall it's reasonably scoped.
Deck lifecycle is thorough (create, get, list, apply_ops for mutation, validate, render, export, history, revert, delete), and brand kits have create/get/list/suggest. Minor gaps: no delete or update for assets and brand kits, which agents may need to clean up.