flat-mcp
Related Servers
Alternatives to flat-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables Claude AI to convert, edit, and analyze MuseScore files (.mscz, .musicxml, MIDI) through natural language commands, supporting format conversion, transposition, harmony analysis, and more.201-
- AlicenseAqualityBmaintenanceEnables AI clients to generate and edit MuseScore scores from compact text notation and export them as mscz, PDF, PNG, SVG, MIDI, or MP3 without opening the MuseScore GUI.11MIT
- AlicenseBqualityCmaintenanceEnables Claude to manage Spotify playlists and analyze personal listening history, including account reads, playlist writes, local analytics from data exports, and building playlists from track lists.35MIT
- AlicenseCqualityBmaintenanceEnables Claude to read and edit a live Dorico 6 score through conversation, with each edit appearing as one ordinary undo step and being read back and verified, undoing it automatically if verification fails.66MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI tools to convert music scores between MusicXML, MIDI, ABC, MEI and Humdrum while verifying each result note by note and reporting exactly what was kept or lost. Also supports rendering printable sheet music and audio previews, transposing, extracting parts or bars, validating bars, and comparing versions across formats.48 PyPIMIT
- FlicenseNot gradedqualityCmaintenanceEnables managing Google Drive files, Docs, and Sheets through natural language via Claude Code, with tools for listing, searching, editing, and formatting documents and spreadsheets.-
TDQS
Scored across 16 tools
The four write paths (flat_upload_revision, flat_replace_measures, flat_edit_musicxml, flat_restore_revision) all produce new revisions but operate at clearly different granularities (whole score, measure range, exact text substitution, revert), and the descriptions spell this out. The only mild overlaps are flat_get_measures vs flat_get_musicxml and flat_score_overview vs flat_get_musicxml, which are differentiated by range/pagination.
Almost every tool follows a flat_verb_noun pattern in snake_case (flat_create_score, flat_list_scores, flat_replace_measures), which is highly predictable. The lone deviation is flat_score_overview being noun-first, plus flat_whoami which lacks a noun but is a recognizable idiom.
16 tools is slightly on the heavy side but each maps to a plausible, non-redundant operation in a music-score editing lifecycle (read, edit, history, export, account). Nothing feels padded, though the set could be tightened by merging the two MusicXML getters.
Create, read (overview, measures, raw XML), update (metadata, measures, text, whole-score), fork, revision history/restore, and multi-format export are all covered, so most workflows reach no dead end. The notable gap is deletion/trashing of scores (the 'trash' collection is listed but no tool moves a score there) and collaboration management.