@jam-jam/convert-mcp
Related Servers
Alternatives to @jam-jam/convert-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides AI-powered audio generation and processing through the MusicGPT API, enabling music creation, voice conversion, audio manipulation, stem extraction, and audio analysis capabilities.2431 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI apps to search song sheet music, MIDI, and isolated stems, inspect available parts and notation levels, and retrieve song pages, printable PDFs, and Guitar Pro files without sign-in.MIT
- FlicenseNot gradedqualityCmaintenanceEnables musicians and their agents to manage AI licensing, register tracks by ISRC, issue/revoke licences, access compliance audit trails, and run their artist platform (merch, events, subscriptions, crowdfunding) through natural language with 46 tools.13 npm1-
- AlicenseNot gradedqualityCmaintenanceEnables users to turn a description of who a song is for into original lyrics, two complete song versions, and cover art through an AI assistant or compatible MCP/OpenAPI client. It also supports revising song plans, replacing sections, stem separation, and library/credit management.54 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI music generation and management through the Suno API, supporting text prompts, custom lyrics, track status monitoring, and credit management.16-
- 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
TDQS
Scored across 42 tools
The domains (conversion, notebook, social, stems, audio analysis, AI detection, mastering) are mostly distinct, with domain prefixes helping distinguish similar operations. However, there are several parallel 'get job' tools (jj_get_job, jj_queue_get_job, jj_stems_get_job, jj_ai_music_get_job, jj_mastering_get_job) and parallel capability/availability tools that could be confused at a glance, especially because the conversion tool uses the unqualified jj_get_job.
Most tools follow a jj_verb_noun pattern, but the convention is mixed: some place the domain first (jj_mastering_get_job, jj_stems_get_job), others place the verb first (jj_list_mastering_presets), and the audio analysis domain splits between jj_audio_analyze and jj_queue_* tools. The same concept is also named inconsistently across domains (capabilities vs availability), and jj_get_job lacks a domain prefix unlike its siblings.
42 tools is well beyond the 25-tool threshold and imposes a large selection burden even though the server spans many sub-domains. Each domain is internally coherent and most tools earn their place, but the overall surface is too large for an agent to navigate comfortably without scoping or grouping.
The notebook (songs and playlists) has full CRUD, and stems, AI music detection, and mastering each have discovery, submission, polling, download, and cancellation paths. Minor gaps remain: mastering presets can only be created and listed, not updated or deleted, and there is no way to list past mastering render jobs, while social tools correctly omit follow/unfollow as app-only.