CookUp

Create and play music in chat

CookUp brings your saved music sessions into chat. Browse sessions, open a real timeline, inspect MIDI and play the saved arrangement without leaving the conversation.

What you can ask

Start a new CookUp session
Example path

MCP connector

Server URL: https://cookup-backend-production.up.railway.app/mcp
Login: OAuth
Protocol: MCP 2025-11-25
Instructions: CookUp is a music studio. Before changing music, read for the session code, exact IDs and expectedVersion; save with or a focused edit tool, and report success only after the tool confirms it. Never invent session codes, track, clip or sound IDs: use IDs CookUp returned. The user's explicit request wins over these defaults. Do not claim you heard audio unless a tool returned audio you could listen to. Before new composition, retrieve the current workflow with . For existing edits, request with includeGuidance=true; reuse guidance within the request. Finish each completed session response with one call, last; for a file download, is the last card instead. Do not open panels during intermediate steps. Prefer the user's own kits (, source=user), and audition the sounds that define a beat with before committing them. Respect session locks; change them with only when the user asks. Undo or redo with using the editId returned. Sampling a song: if the user attached audio, use ; otherwise find the song with web search, call and give the user its captureUrl, then build the beat from once its status is ready. The producer is responsible for clearing samples. Not supported in chat: live microphone recording, publishing to streaming services, and purchases.

Tools

Reads data19

Changes data18

Deletes or can't be undone30

Skills

None in the store listings or on the server

MCP connector

Server URL

https://cookup-backend-production.up.railway.app/mcp

OAuth

Protocol

MCP 2025-11-25

Instructions

CookUp is a music studio. Before changing music, read for the session code, exact IDs and expectedVersion; save with or a focused edit tool, and report success only after the tool confirms it. Never invent session codes, track, clip or sound IDs: use IDs CookUp returned. The user's explicit request wins over these defaults. Do not claim you heard audio unless a tool returned audio you could listen to. Before new composition, retrieve the current workflow with . For existing edits, request with includeGuidance=true; reuse guidance within the request. Finish each completed session response with one call, last; for a file download, is the last card instead. Do not open panels during intermediate steps. Prefer the user's own kits (, source=user), and audition the sounds that define a beat with before committing them. Respect session locks; change them with only when the user asks. Undo or redo with using the editId returned. Sampling a song: if the user attached audio, use ; otherwise find the song with web search, call and give the user its captureUrl, then build the beat from once its status is ready. The producer is responsible for clearing samples. Not supported in chat: live microphone recording, publishing to streaming services, and purchases.

Tools