Splice MCP
Splice MCP lets agents search the sounds catalog, build and edit stacks, share stacks, and download eligible sounds using Splice credits.
Verdict
Common use cases
- Find samples matching a creative brief
- Preview loops before downloading to DAW
- Curate sound packs for client projects
- Search by genre and tempo constraints
- Pull metadata on trending sounds
Integration
- Vendor
- Splice MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
splice_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Splice MCP in the list and click Connect. 3. You'll be redirected to Splice's authorization page — log in with your Splice account credentials. 4. Review the requested scopes (typically library read access and search permissions) and click Authorize. 5. Switchy will confirm the connection and return you to the integrations page. 6. Open any Project and type '@Splice' followed by a request like 'find trap hi-hats with a crisp attack' to test the connection. 7. If the MCP responds with sample suggestions or search results, the setup is complete. 8. If you see an error, revisit Settings > Integrations and reconnect, ensuring you grant all requested scopes.
What teammates see: by default, memories from Splice MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Find Vocal Chops
@Splice find vocal chops in the 120-128 BPM range, preferably in C minor, suitable for a deep house track.
Recommend Drum Loops
@Splice recommend five breakbeat drum loops with high energy, suitable for a DnB production around 174 BPM.
Preview Bass Samples
@Splice show me sub bass samples with a warm, analog character, ideally under 60 Hz fundamental.
Search by Mood
@Splice search for ambient pads and textures tagged as 'melancholic' or 'cinematic' for a film cue.
Check Trending Sounds
@Splice what are the trending trap samples this week? Focus on 808s and snares.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@splice show me the latest sample packs added to my library this month, organized by genre
Based on your Splice library activity, here are the sample packs added in the last 30 days: **Hip-Hop/Trap**: 'Urban Heat Vol. 3' (142 samples), 'Lo-Fi Drums Essentials' (89 samples) **Electronic**: 'Modular Synthesis Toolkit' (203 samples), 'Techno Percussion' (156 samples) **Indie/Alternative**: 'Bedroom Pop Starter Kit' (67 samples) Total: 5 packs, 657 samples. Most downloads occurred between Jan 15-18.
This example assumes the MCP can read library metadata and organize by user-defined criteria. Requires OAuth scope for library access. Response time depends on library size — accounts with 500+ packs may see slower queries.
@splice create a new collection called 'Q1 2025 Project Drums' and add all kick and snare samples I downloaded in January
Collection created successfully. **Q1 2025 Project Drums** now contains: - 47 kick samples (from 8 packs) - 34 snare samples (from 6 packs) Samples were filtered by download date (Jan 1-31, 2025) and instrument tag. The collection is now visible in your Splice app under 'My Collections'. You can add more samples or share this collection with collaborators.
Demonstrates write capability — creating collections and batch-organizing samples. This action modifies your Splice account state immediately. If the MCP lacks granular tag filtering, you may need to manually verify the collection contents match your intent.
@splice analyze my download history and suggest three sample packs I haven't tried yet that match my production style
Based on 6 months of download patterns (heavy use of analog synth one-shots, minimal vocal chops, preference for 120-130 BPM loops), here are three recommendations: 1. **'Analog Dreams'** by Capsun ProAudio — modular synth textures, no vocals, avg 125 BPM 2. **'Warehouse Techno'** by Splice Originals — raw drum machines, industrial percussion 3. **'Minimal House Essentials'** — clean basslines and subtle melodic loops Each pack aligns with your genre tags (house, techno) and avoids vocal-heavy content you typically skip.
This synthesis example pairs your usage data with the AI's pattern recognition to surface relevant packs. Accuracy depends on how much download history exists — new accounts get generic suggestions. Recommendations reflect Splice's catalog at query time, not real-time availability.
Use-case deep-dives
When Splice MCP makes sense for video or podcast workflows
A 3-person video production team cuts 8-12 short-form videos a week and needs royalty-cleared music loops fast. Splice MCP connects your workspace to Splice's sample library through OAuth2, so the AI can search and preview audio without leaving the conversation. This works if your team already subscribes to Splice and you're tired of context-switching to the web app mid-edit. The trade-off: OAuth2 setup takes 10 minutes, and if your team doesn't already use Splice, you're adding a new subscription just to enable the MCP. If you're producing fewer than 5 videos a month, the manual workflow is probably fine. For teams shipping daily, the MCP pays off by keeping audio decisions in the same thread as script and edit notes.
Splice MCP for producer teams sharing sample packs
A 2-person music production duo works on client tracks and needs to pull from the same Splice sample library without emailing WAV files back and forth. Splice MCP lets both producers query the library through Switchy's shared workspace, so sample selection happens in the same thread as mix notes and client feedback. This setup makes sense if you're both on Splice already and you collaborate on 3+ projects a month. The boundary: if one producer uses a different sample service or you're working solo, the MCP adds OAuth overhead without the collaboration payoff. For duos or small production teams that live in Splice daily, the MCP keeps sample decisions visible and searchable in your project history.
When Splice MCP fits a weekly podcast production schedule
A 4-person podcast team publishes one episode a week and needs background music, transitions, and sound effects for each 30-minute show. Splice MCP connects the team's Splice account so the AI can search and suggest audio during episode planning calls. This works if your team already pays for Splice and you're spending 20+ minutes per episode hunting for the right loop. The trade-off: OAuth2 means each team member authenticates once, and if your show uses the same 5 tracks every week, the MCP is overkill. For teams experimenting with sound design or producing multiple shows, the MCP keeps audio decisions in the same workspace as show notes and guest prep. If you're publishing less than twice a month, the manual search is faster.
Frequently asked
What does Splice MCP do in Switchy?
Splice MCP connects your Switchy workspace to Splice's audio sample library and project data. Since no specific tools are documented yet, expect read access to your samples, loops, and project metadata. Your team can query Splice content without leaving the AI workspace, useful for music production teams coordinating around shared sound libraries.
Do I need a paid Splice account to use this MCP?
Yes. Splice MCP uses OAuth2, which means you authenticate with your existing Splice credentials. If your account is free-tier, the MCP will inherit those limits—restricted sample downloads, no access to premium packs. The integration doesn't bypass Splice's subscription tiers; it just surfaces your existing access inside Switchy.
Can Splice MCP download samples directly into my DAW?
No. MCP integrations run inside Switchy's AI workspace, not your local machine. You can search and reference Splice content through the AI, but actual file downloads still happen through Splice's desktop app or web interface. Think of this as a metadata bridge, not a file-transfer tool.
Why use Splice MCP instead of just opening Splice in a browser tab?
The MCP lets your AI agents query Splice data programmatically—search by BPM, key, genre, or project history without manual clicks. If your team discusses production ideas in Switchy, the AI can pull relevant samples mid-conversation. You skip the context-switch tax of tabbing between tools.
Who on the team should connect Splice MCP to Switchy?
Whoever owns the Splice account your team uses for production. If you share a Splice subscription, connect it once under that account. Individual producers with separate Splice logins can each connect their own, but you'll fragment the sample library your AI can reference. One shared connection usually makes more sense.