Splice MCP
for LuumenAI

Search the Splice catalog, build stacks, and download sounds with approval

Connect Splice and the agent can search the sounds catalog in plain language, then act on what it finds. Ask for a texture or a tempo and get candidates back right away. Building a stack, sharing it, editing it, or spending credits on a download is previewed first and, by default, waits for your approval. Sign-in uses OAuth.

Book a DemoDownload Luumen

The Splice MCP toolbox

6 tools: 1 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadDescribe a soundSearch the Splice catalog for sounds matching a natural language description.
  • WriteCreate stackCreate a stack from an existing sample. Approval by default
  • WriteDownload assetPurchase and get a presigned download URL for a sound from the Splice catalog. Approval by default
  • WritePrompt to stackGenerate a complete multi-track arrangement of compatible samples from a text description. Approval by default
  • WriteShare stackGenerate a public shareable URL for an existing stack. Approval by default
  • WriteUpdate stackModify an existing stack. Approval by default

One prompt, start to finish

What a governed Splice MCP run looks like inside Luumen.

Questions

How does LuumenAI connect to Splice MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Splice MCP on its own?

Read actions answer immediately. Anything that writes — create stack, download asset, prompt to stack, share stack, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Splice MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task statusAffindaRead parsed documents, collections, and annotations — change them with approvalAgent MailGive the agent its own mailbox for reading threads and sending updatesAI/ML APIInspect assistants, threads, and runs — and change them as approved steps

Put Splice MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a DemoDownload Luumen