merlin-slides-mcp
Related Servers
Alternatives to merlin-slides-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to create, inspect, and edit self-contained HTML presentation decks through semantic tools, validate them against the htmldeck/v1 contract, hand them to a local visual editor, and export them as standalone HTML, PDF, or per-slide PNG.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
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents to generate, edit, export, and preview AI slide decks through tool calls. Supports deck generation from topics or reference material, per-slide and deck-wide edits, and HTML export.2MIT
- FlicenseCqualityCmaintenanceEnables conversational, deterministic inspection, editing, rendering, and validation of PowerPoint (.pptx) presentations, allowing agentic creation and modification of slides with style preservation and visual verification.34-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create professional Slidev presentations and export them to PDF directly through natural language commands. Supports multiple themes, code syntax highlighting, and various slide layouts for business, technical, and educational content.1MIT
- AlicenseAqualityBmaintenanceEnables AI hosts to validate, write to disk, hot-reload, preview, and export single-file HTML prototypes built to the Spark OP design spec, serving them locally at 127.0.0.1:5179 by slug. Also bundles the triggering skill, spec references, templates, and CSS tokens so agents can create, revise, and hand off development-ready prototype HTML through one controlled output path.920 npmMIT
TDQS
Scored across 2 tools
Each tool targets a clearly distinct operation: build_deck produces HTML output, while check_outline performs validation only. There is a natural pre-flight/build relationship but no overlap in behavior, so an agent can easily choose the right tool.
Both names use snake_case with a verb_noun structure (build_deck, check_outline), which is consistent in style. The verbs differ in category (build vs check) but each accurately describes its action, so this is a minor, acceptable deviation.
Only two tools exist, which is thin for a deck-building domain; content authoring, theming, and export are unaddressed. The pair is logically coherent but borderline minimal, leaving an agent with limited leverage.
The surface covers the core validate-then-build flow, which is a complete minimal lifecycle. However, there are notable gaps: no way to preview slides, customize styling, or edit an existing deck, so agents may hit dead ends for non-trivial presentations.