Skip to main content
Glama

Related Servers

Alternatives to Flow Learning System

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables teachers to turn plain-language teaching requests into interactive HTML demos and Mannim-rendered narrated animations through a confirm-once workflow, with automatic lesson design, generation, review, and revision. Shares a local work library with the standalone web workbench so finished lessons can be exported as offline HTML, MP4, or ZIP packages.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets coding agents drive the full PDF-to-lesson pipeline — ingesting, planning, storyboarding, translating, narrating, QA-ing and exporting — or author lesson beats themselves while the server validates and renders them. It enables agents to produce offline, animated, narrated, interactive books with in-picture questions.
      1
      Apache 2.0
    • F
      license
      A
      quality
      B
      maintenance
      Enables AI agents to generate dimensionally accurate mechanical parts (gears, enclosures, brackets, assemblies) in headless Blender from plain-English specs or JSON parameters, then verify them against manifold, bounding-box and print-production gates and export glTF/STL assets. It also scaffolds interactive Three.js CAD viewer pages with orbit controls, wireframe toggles and exploded-view scrubbing.
      4
      115
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to generate and validate multi-granularity storyboard assets from text prompts, including 2D SVG motion, 3D Blender depth/blockout, and SDXL ControlNet final images. It also supports vision-based self-correction and a SQLite knowledge database of successful recipes.
      MIT

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool maps to a distinct stage of the authoring pipeline (init → guide → lesson_get/save/validate → speech_preview/audio_synthesize → render_3d → course_build), so selection is mostly unambiguous. Minor overlap exists between lesson_validate and lesson_save (which also validates), and between speech_preview and audio_synthesize (both deal with TTS text/audio).

    Naming Consistency4/5

    The dominant convention is noun_verb (lesson_get, lesson_save, lesson_validate, course_init, course_build, course_status, assets_list, speech_preview, pronunciation_add, code_verify, audio_synthesize), which is predictable. Deviations are small: render_3d is verb-first and authoring_guide has no verb at all.

    Tool Count5/5

    13 tools is well within the ideal range and each covers a discrete authoring concern (course scaffolding, lesson CRUD/validation, speech, 3D assets, build, status, docs). No obvious filler tools or redundant wrappers.

    Completeness4/5

    The lesson and course lifecycle is well covered: init, get, save, validate, status, build, plus speech and asset generation. Gaps are minor but real — there is no lesson delete/list-by-id beyond course_status, no way to remove or inspect registered pronunciations, and no asset deletion tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues