Skip to main content
Splice MCP logo
  • Category: model context protocol
  • Auth: DCR_OAUTH
  • Composio-managed OAuth available? No
  • Tools: 6
  • Triggers: 0
  • Slug: SPLICE_MCP
  • Version: 20261018_00

Tools

Slug: SPLICE_MCP_CREATE_STACKCreate a stack from an existing sample. This is the ONLY tool that can use a previously found or selected sample as a seed — if the user wants to build a stack around a specific sample, you MUST use this tool (not prompt_to_stack). ROUTING RULE: Any request like ‘create a stack from this sample’, ‘build around this loop’, ‘use this as a seed’, or referencing a specific asset UUID MUST use this tool. The seed sample MUST be a loop (not a one-shot). If the user asks to build a stack from a one-shot, do NOT silently search for loops. Instead, FIRST explain to the user that one-shots cannot be used as stack seeds because stacks require loopable samples to layer together, THEN offer to find similar loops that match the style or character of the one-shot they liked. Uses the loop as the starting layer and generates a full multi-layer stack of compatible samples around it.

Input Parameters

integer
Target BPM for the stack (e.g. use the seed sample’s BPM). Omit to let the backend decide.
string
An optional name for the stack
string
required
The UUID of the sample to use as the seed for the stack
boolean
Set to true ONLY if the user explicitly asks for a shareable, public, or web link. Defaults to false.
Slug: SPLICE_MCP_DESCRIBE_A_SOUNDSearch the Splice catalog for sounds matching a natural language description. Returns sample metadata including BPM, key, tags, duration, and Splice links. Use this to BROWSE and EXPLORE individual sounds — when the user wants to find, preview, or discover specific samples, loops, or one-shots. Do NOT call this tool alongside prompt_to_stack for the same request. If the user wants a complete multi-track beat or arrangement, use prompt_to_stack instead. Present ALL results to the user exactly as numbered; do not filter, omit, or reorder any results — let the user decide which sounds are relevant. IMPORTANT: One-shots CANNOT be used as seeds to create stacks — only loops can. If the user searched for one-shots and then asks to create a stack from those results, you MUST explicitly tell the user that one-shots cannot be used to create stacks and offer to search for similar loops instead. Do NOT silently pivot to loops.

Input Parameters

string ("loop" | "oneshot")
Sample type: loop or oneshot
string
required
Natural language description of the sound you are looking for
integer
Maximum BPM filter
integer
Minimum BPM filter
Slug: SPLICE_MCP_DOWNLOAD_ASSETPurchase and get a presigned download URL for a sound from the Splice catalog. The server returns a presigned URL — it does not write files. If the client has local filesystem access, it should fetch the URL and save the file to download_path; otherwise omit download_path and present the URL to the user. IMPORTANT: The first time an asset is downloaded it spends one of the user’s credits. Subsequent downloads of the same asset are free. Always confirm with the user before calling this tool. The URL expires quickly — always display the file name alongside the download URL so the user can identify and access their file.

Input Parameters

string
required
UUID of the asset to download
string
Optional hint indicating where the client should save the downloaded file. The server returns a presigned URL; the client is responsible for fetching and saving the file. Omit when the client does not have local filesystem access (e.g. web-based clients).
Slug: SPLICE_MCP_PROMPT_TO_STACKGenerate a complete multi-track arrangement of compatible samples from a text description. Use this ONLY when the user describes a sound from scratch without referencing a specific existing sample. This tool does NOT accept a sample UUID as input — it creates a stack entirely from a text prompt. ROUTING RULE: If the user says anything like ‘create a stack from this sample’, ‘build a stack around this loop’, or ‘use this as a seed’, you MUST use create_stack instead — even if the user also provides a text description of the desired sound. Do NOT call this tool alongside describe_a_sound for the same request. If the user just wants to browse or find individual sounds, use describe_a_sound instead. Uses AI to interpret your prompt, select appropriate instrument layers (drums, bass, keys, etc.), and filters, and find matching harmonically coherent samples. BPM GUIDANCE: Always include a target BPM in the prompt AND set bpm_min/bpm_max to avoid extreme time-stretching. If the user specifies a genre but not a BPM, infer the range from the genre. Optionally generates a public shareable URL.

Input Parameters

string
required
Your prompt describing the sound you want to create (e.g. “lo-fi hip hop beat at 80 bpm with a groovy bassline and jazzy piano”, “an upbeat pop song in the style of Bruno Mars in the key of C major”)
integer
Maximum BPM for sample selection based on the genre. Must be provided together with bpm_min.
integer
Minimum BPM for sample selection based on the genre. Infer from genre when the user does not specify a BPM. Typical ranges: lo-fi/chill 60–100, soulful beats/R&B 70–120, pop 100–130, disco/funk 110–130, house/techno/dance 115–135, industrial/experimental 110–150, drum and bass/jungle 160–180. For genres not listed, ensure at least a 30 BPM spread between bpm_min and bpm_max.
boolean
Set to true ONLY if the user explicitly asks for a shareable, public, or web link. Defaults to false.
Slug: SPLICE_MCP_SHARE_STACKGenerate a public shareable URL for an existing stack. Takes a stack UUID (from a previous create call) and returns a shareable link.

Input Parameters

string
required
UUID of the stack to share
Slug: SPLICE_MCP_UPDATE_STACKModify an existing stack. Use this tool to add, remove, or swap sounds in a stack, rename it, or change its BPM. LAYER LIMIT: Stacks have a maximum of 8 layers. Adding layers beyond this limit will fail. If the stack already has 8 layers, remove existing layers before adding new ones. Required parameter: stack_uuid (the UUID, not a URL). To remove layers, pass their UUIDs via remove_layer_uuids. At least one modification must be provided. When adding or swapping layers, PREFER add_compatible_layers and swap_compatible_layers — these find harmonically compatible samples that fit the existing stack. Only use add_asset_uuids or swap_layers when the user has explicitly chosen a specific sample to use. DRUMS: When adding drums, ALWAYS include the ‘grooves’ tag in the tag_filter (e.g. ‘(hip hop || trap) && grooves’, ‘house && grooves’) to get complete drum patterns (kick + snare + hats combined). Without the ‘grooves’ tag, the search returns isolated single-hit layers (just kicks, just snares, etc.) instead of full drum loops. Only omit ‘grooves’ if the user explicitly asks for an isolated drum element. Optional tag filter DSL to narrow sample selection. Prefer && (intersection) so all tags must match for precise results; fall back to || (union) only if intersection returns too few results. Valid tags per layer type: drums: grooves, house, hip hop, techno, tech house, hats, live sounds, trap, deep house, kicks, edm, pop, downtempo, snares, percussion, rnb; percussion: live sounds, house, techno, hip hop, tech house, cinematic, shakers, trap, downtempo, acoustic, deep house, edm, synth, pop; bass: synth, house, sub, techno, hip hop, tech house, edm, electric, trap, deep house, drum and bass, rnb, downtempo, dubstep; guitar: electric, live sounds, electric guitar, hip hop, acoustic, rnb, pop, rock, trap, soul, wet, funk, downtempo, lo-fi hip hop, dry; keys: piano, hip hop, electric piano, synth, rnb, soul, trap, live sounds, house, downtempo, pop, lo-fi hip hop, organ, deep house, jazz; strings: live sounds, hip hop, organic, acoustic, cinematic, synth, cello, folk, dry, clean, violin, trap, rnb, soul; vocals: female, pop, wet, edm, live sounds, dry, male, rnb, house, hip hop, pitched, cinematic, trap, soul, future bass; chords: synth, keys, hip hop, rnb, piano, guitar, live sounds, soul, trap, house, electric, pop, electric piano, downtempo, lo-fi hip hop; leads: synth, house, edm, wet, trap, techno, hip hop, pop, vocals, tech house, progressive house, rnb, guitar, deep house, trance; pads: synth, hip hop, house, downtempo, trap, techno, ambient, rnb, cinematic, pop, synthwave, deep house, edm, tech house, soul; brass-and-woodwinds: live sounds, hip hop, trap, organic, synth, cinematic, dry, acoustic, jazz, rnb, soul, clean; synth: house, techno, hip hop, trap, tech house, edm, deep house, downtempo, pop, rnb, progressive house, sub, wet, synthwave, future bass; fx: synth, techno, house, cinematic, ambient, edm, hip hop, vocals, percussion, downtempo, tech house, live sounds, trap, pop

Input Parameters

integer
New playback BPM for the stack
string
New name for the stack (max 64 characters)
string
required
The UUID of the stack to modify (returned as Stack UUID by create_stack or prompt_to_stack). Use the UUID value, not a URL.
string
Layers whose sample content should be replaced with a specific asset. Mutually exclusive with swap_compatible_layers.
string
Asset UUIDs to add as new layers at the end of the stack. Mutually exclusive with add_compatible_layers.
string
Layer UUIDs to remove from the stack (use the Layer UUID values shown in the stack output)
string
Layers to add using harmonically compatible samples. Specify the instrument type for each layer. Mutually exclusive with add_asset_uuids.
string
Layers to swap with harmonically compatible replacements. Mutually exclusive with swap_layers.