Skip to main content
Glama
Rotvie

decksmith

by Rotvie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to decksmith

No user-submitted related servers found.

    Related Servers

    • jh-presentation

      pei-jz
      A
      license
      Not graded
      quality
      A
      maintenance
      Turns 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.
      417 npm
      MIT

    • PresentFlow

      Dibyendu-13
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Desktop users to generate structured, editable PowerPoint decks from a natural-language brief and slide-count settings by triggering the n8n presentation pipeline. Returns the generated title, presentation ID, and a downloadable PPTX link.
      -

    • Cicero

      Luissalet
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct pipeline stage (init, plan, approve, briefs, preview, generate, status, regenerate), which makes most boundaries clear. The one overlap is preview_deck_generation vs preview_slide_prompt — one previews all prompts and returns an approval token, the other previews a single brief — but the descriptions distinguish them well enough.

    Naming Consistency5/5

    The set follows a consistent verb_noun snake_case pattern throughout: list_visual_systems, initialize_deck, submit_deck_plan, approve_plan, submit_slide_briefs, mark_slide_for_regeneration, preview_deck_generation, generate_deck_images, get_deck_status, preview_slide_prompt. No mixed conventions or stray camelCase.

    Tool Count5/5

    10 tools is well within the ideal range and each maps to a concrete step in a deck-generation workflow. None appear redundant or trivial filler.

    Completeness4/5

    The surface covers the full lifecycle from initialization through plan approval, brief submission, preview, paid generation, status inspection, and per-slide regeneration. Minor gaps remain — no explicit finalize/export of the assembled deck and no cancel/cleanup operation — but core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources