Skip to main content
Glama
btdt

famistudio-mcp

Official
by btdt

Related Servers

Alternatives to famistudio-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a headless video editing workflow using portable JSON projects and Kdenlive for review, enabling automated video rendering and project management.
      7
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables bounded, schema-validated automation of FMOD Studio game audio through MCP/CLI workflows, including inspection, safe mutations, previews, receipts, and high-level workflows for events, assets, parameters, adaptive music, spatial audio, banks, and mixer/routing.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables editing Scratch .sb3 projects programmatically, including sprites, blocks, costumes, sounds, variables, and online project sharing, plus headless VM execution and live-reload in TurboWarp Desktop.
      4
      43
      18 npm
      Mozilla Public 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading, writing, and validating .tldr files for tldraw, a headless implementation without browser dependencies.
      MIT

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation3/5

    Several tools sit close together: compile_song_spec vs create_fms, validate_fms vs verify_roundtrip, read_fms vs summarize_fms, and export_audio vs analyze_audio. The descriptions do clearly separate in-memory creation from file writing, invariant checks from end-to-end verification, and structured decoding from human-readable review, but an agent must read them carefully to avoid misselection.

    Naming Consistency4/5

    Most tools follow a clean verb_noun snake_case pattern such as compile_song_spec, validate_fms, and export_audio, with the repeated _fms suffix forming a recognizable family. The main deviations are famistudio_info, which is noun-style, and run_famistudio, which uses the application name as the object.

    Tool Count5/5

    Thirteen tools is a well-scoped size for a specialized FamiStudio server, and each tool maps to a distinct part of the create-validate-export-review workflow. None feel redundant or extraneous.

    Completeness4/5

    The server covers the full core loop: environment info, tempo arithmetic, spec compilation, file writing, validation, round-trip verification, reading, summarizing, diffing, audio analysis, and audio/text export. A minor gap is the lack of a direct update/modify path for an existing project from structured JSON, though run_famistudio acts as an escape hatch for uncovered CLI operations.