famistudio-mcp
OfficialRelated Servers
Alternatives to famistudio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides a headless video editing workflow using portable JSON projects and Kdenlive for review, enabling automated video rendering and project management.7Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseBqualityCmaintenanceEnables 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.44318 npmMozilla Public 2.0
- AlicenseAqualityCmaintenanceEnables an AI agent to compose chiptune music by directly reading and writing Lovely Composer's .jsonl project files, including melodies, bass, drums, chords, tempo, and loop points.121MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading, writing, and validating .tldr files for tldraw, a headless implementation without browser dependencies.MIT
- AlicenseBqualityBmaintenanceEnables headless Blender asset QA and FBX reimport verification for game and 3D asset pipelines, checking mesh count, material count, and naming prefixes with deterministic JSON results.3206 npm2MIT
TDQS
Scored across 13 tools
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.
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.
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.
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.