Look up a music production by its ID to retrieve metadata and an audio URL. Check whether stem separation, which splits audio into parts, MIDI extraction, or mastering has finished using the production’s latest status.
Fetch metadata and audio_url for a single production by id
Review the instructions the agent will receive before you install.
Looks up one production's current state — useful to check whether a separate_stems/extract_midi/master call from earlier in the session actually finished.
You have a production id (from music-generate's result, music-list, or the music-productions memory cache) and need its latest metadata.
music-productions namespace cache first if you're only after fields that don't change (title, original prompt/lyrics, audio_duration) — no need to round-trip if you already have them.has_stems, has_midi, has_mastered, lufs_before/lufs_after), call the live tool:
mcp__cogmusic__get_production({ id: "<production-id>" })
id doesn't exist or belongs to a different account, the call errors — don't guess at a substitute id; ask the user to confirm it or run music-list to find the right one.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.