Head to head · Music search · October 2026 research run
Epidemic Sound MCP Server vs Slipstream
Slipstream scores 50 (D) on agent readiness against Epidemic Sound MCP Server's 24.5 (F), and leads in 6 of 7 scored categories. Epidemic Sound MCP Server leads on maintenance & community. Both do music search.
Best music and sound libraries for AI agents · All 21 music libraries comparisons
Which one, for what
Best for An agent soundtracking video for a person who already pays for Epidemic Sound.
Ahead on
- Maintenance & community, 40 against 18
Watch for
Labelled beta, with rate limits stated as unpublished and no status page or changelog found
Best for An agent helping a Slipstream subscriber find, clip and clear music for video, or an enterprise issuing rate-card licences with approval.
Ahead on
- Reliability, 80 against 5
- Schema & documentation, 50 against 29
- Agent ergonomics, 60 against 35
- Security & auth, 47 against 28
- Payments & pricing, 25 against 15
- Transparency & trust, 37 against 32
Watch for
An initialize with no token answered 401 on 22 November 2026, so the catalogue tools the docs call public were not reachable without signing in
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Slipstream +75
Epidemic Sound MCP Server 5
Hosted MCP reading of the checklist. No status page found (0). No readable incident history (5). The MCP docs say rate limits aren't published (0). No 429, overload or retry guidance for the MCP server. The REST API's error page documents 429 with a retry delay, but that is a different product with different keys (0). No SLA found (0). The server and its docs are labelled beta (0). 0 + 5 + 0 + 0 + 0 + 0 = 5.
Slipstream 80
Atlassian Statuspage at status.slipstreammusic.com with Platform and API components and no MCP component (20). The history page and its RSS feed list no incidents, and the last 15 days each read no incidents reported (30). Partner quotas are daily and monthly with a burst limit per key, but the only numbers (1,000 a day, 30,000 a month) are an example usage block, and no limits are given for OAuth users (5 of 15). The licence endpoint returns 429 throttled with Retry-After and is safe to repeat for the same user, track and project, and async MCP tools are polled with identical arguments (15). No SLA found on the pages read; the main site could not be read (0). The MCP server and API carry no beta label (10). 20 + 30 + 5 + 15 + 0 + 10 = 80.
Agent ergonomics Slipstream +25
Epidemic Sound MCP Server 35
16 tools, in the 11 to 30 band (15). No toolsets or read-only subset an operator can choose. Claude's directory connector drops the voiceover tools, which is the directory's rule, not a control (0 back). Search takes genre, mood, BPM, key and more per the docs, and maxResults appears, with no pagination described (10). A 401 is documented and doesn't say why. No other MCP errors are documented (5). Tool annotations and idempotency couldn't be read, and edits and voiceovers are poll-until-done jobs with no retry guidance (0). No MCP SDK of its own, and the docs point to the official TypeScript SDK. Workflows need several calls and IDs from earlier ones (5). 15 + 10 + 5 + 0 + 5 = 35.
Slipstream 60
MCP reading. 56 tools with no toolsets, dynamic loading or read-only subset (5 of 25). Search takes genre, mood, vocals, BPM and duration filters, REST search takes limit and offset with next and previous links, and an over-tight filter stack is relaxed and reported in relaxed_filters (15 of 20). REST errors return success: false with a stable code and a message, and the MCP docs say a capped call returns a clear message, with already-added channels and videos returning success (15 of 20). The docs say every tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint, licences are idempotent for the same user, track and project, and renders are polled with identical arguments, not verified in tools/list (18 of 20). Few required parameters, and six registered prompts, but no official SDK (7 of 15). 5 + 15 + 15 + 18 + 7 = 60.
Maintenance & community Epidemic Sound MCP Server +22
Epidemic Sound MCP Server 40
Closed hosted service. The vendor's MCP blog post, dated 13 October 2026, says it was updated for changes to the server, the newest dated change found (20). The registry's 1.0.1 is from 17 August 2026 and the Claude directory launch from 31 August 2026, so fewer than three dated changes in the last 90 days (0). No public changelog. Support goes through a help centre form, and the help centre answered 403 to us (5). Verified namespace com.epidemicsound/mcp-server in the MCP registry (15). No package to judge (0). 20 + 0 + 5 + 15 + 0 = 40.
Slipstream 18
Closed-service reading. No dated API or MCP change could be read because the changelog loads by script and its feeds answered 405. The newest dated page about the MCP is the help centre guide of 3 August 2026, within 180 days (10 of 30). Dated changelog entries in the last 90 days unchecked (0 of 20). A changelog page that promises advance notice of breaking changes, support by chat and support@slipstreammusic.com with a stated 24 to 48 hour reply (8 of 15). No entry in the official MCP registry, and no official SDK (0 of 15). No package to judge (0 of 10). 10 + 0 + 8 + 0 + 0 = 18.
Schema & documentation Slipstream +21
Epidemic Sound MCP Server 29
The tool definitions couldn't be read, because robots.txt disallows /a/* and the endpoint sits at /a/mcp-service/mcp. The docs say tools/list returns each tool's description and parameters, but we didn't see them (0). www.epidemicsound.com/llms.txt is a site index that links the MCP page, with no Markdown copy of the MCP docs (5). The docs group the 16 tools by area, give three multi-step workflows and a known-limitations table that says when a tool fails (8). Parameters named in the docs include externalID, targetDurationMs up to 300,000, requiredRegionsAtOffsets, maxResults, skipStems and a language code from a voice's list, with no full input schema (5). curl examples for initialize and tools/list, client configs for four clients and a documented 401, with no other error responses (8). Registry versions 1.0.0 and 1.0.1, no public changelog (3). 0 + 5 + 8 + 5 + 8 + 3 = 29.
Slipstream 50
The docs say tool inputs and outputs are typed, but tools/list could not be read because initialize answered 401, and the REST API has no OpenAPI file or other contract linked (10 of 25). No llms.txt (404) or Markdown docs for agents (0). The tools page states each tool's purpose and when to use it, for example soundtrack_a_video only when no video is attached and get_track_download_url as a download, not a licence (15 of 20). Filter values come from get_search_filters, audio_type takes three values and stems take separate id lists, but no schema was read (8 of 15). End-to-end flows for soundtracks, AudioVerify, allowlists and licences, and REST error tables with stable codes (12 of 15). REST paths are versioned (/api/v4/, /api/v1/) and a changelog page exists, but its entries load by script and its feeds answered 405 (5 of 15). 10 + 0 + 15 + 8 + 12 + 5 = 50.
Security & auth Slipstream +19
Epidemic Sound MCP Server 28
OAuth 2.1 with Dynamic Client Registration on the vendor's own login server, limited to an allowlist of redirect URIs to counter phishing, with SSO and a workspace choice. The only scopes are email and openid, so access isn't narrowed by scope. The bearer key reaches the account, expires after a year and is rotated by making a new one, with no revocation described (20). No read-only mode or approval step for downloads or voiceover generation found (0). Results are the vendor's own catalogue metadata, plus Spotify track IDs from SearchExternalReferences, with no injection guidance (8). No audit log or per-call record for the account found (0). security.txt answers 404, and no disclosure policy, bug bounty or certification was found on the pages read (0). 20 + 0 + 8 + 0 + 0 = 28.
Slipstream 47
OAuth 2.1 with PKCE and dynamic client registration, but a single mcp scope, and partner REST keys carry scopes such as licenses:generate with revoked and expired states (25 of 30). Licences need a read-only prepare_license step and the user's approval of the fee before generate_license, the docs say tools carry destructive hints, and pricing comes from the caller's own rate card so a caller can't name its fee, but OAuth gives no read-only mode (12 of 20). Results include public playlist names and descriptions written by other users and track lookups from outside links, with no prompt-injection guidance found (5 of 15). Each client shows in the Slipstream admin and can be revoked, and partner responses report usage, with no per-call log found (5 of 15). No security.txt on the developer host and no disclosure policy, bug bounty or certification found; the main site could not be read (0 of 20). 25 + 12 + 5 + 5 + 0 = 47.
Payments & pricing Slipstream +10
Epidemic Sound MCP Server 15
No x402, MPP or L402 (0). Plan names and terms are public, but the prices are drawn by script on the pricing page and weren't readable to us, so this line scores as absent (0, unchecked). A free account can connect, search and preview per the MCP FAQ, with no card step described, but downloads and licences need a paid plan, so half credit (15). A person signs up and buys the subscription in a browser, and only the account holder can make an MCP key (0). 0 + 0 + 15 + 0 = 15.
Slipstream 25
No x402, MPP or L402 (0). Individual ($120 a year) and Teams ($2,400 a year) plan prices are public in the help centre, Enterprise and MCP licence fees come from a negotiated rate card, and single-track prices are on a pricing page we couldn't read (15 of 30). The developer docs say a Free tier can connect, but the help centre's MCP guide asks for an active subscription, both trials need a card, downloads answer 403 for free accounts, and initialize answered 401 without a token (10 of 30). A person signs in through a browser, and partner tokens and keys come by contacting Slipstream (0). 0 + 15 + 10 + 0 = 25.
Score by category
| Category | Weight | Epidemic Sound MCP Server | Slipstream | Edge |
|---|---|---|---|---|
| Reliability | 16% | 5 | 80 | Slipstream +75 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 29 | 50 | Slipstream +21 |
| Agent ergonomics | 13% | 35 | 60 | Slipstream +25 |
| Security & auth | 14% | 28 | 47 | Slipstream +19 |
| Payments & pricing | 10% | 15 | 25 | Slipstream +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 40 | 18 | Epidemic Sound MCP Server +22 |
| Transparency & trust | 7% | 32 | 37 | Slipstream +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 24.5/100 | D 50/100 |
Facts side by side
| Fact | Epidemic Sound MCP Server | Slipstream |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Epidemic Sound | Slipstream Music |
| Hosted endpoint | https://www.epidemicsound.com/a/mcp-service/mcp | https://mcp.slipstreammusic.com/mcp |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Your plan | subscription |
| x402 | no | no |
| Tools exposed | 16 | 56 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | com.epidemicsound/mcp-server | not listed |
| Last release | 2026-08-17 | none |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | couldn't be read | no document linked |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
Verdicts
Epidemic Sound MCP Server
An agent can search a 55,000-track owned catalogue by mood, BPM, key or a reference song, recut tracks to length and download them under the user's subscription. The server is in beta, with no published rate limits, status page or changelog, and every download needs a person's paid plan.
Slipstream
The MCP server documents 56 tools for search, downloads, stems, video soundtracks, rights checks and enterprise licences, and its licence flow waits for the user to approve the fee. Every call we could make needed a signed-in subscriber or a partner token, the REST API takes partner keys only, and the terms and privacy policy could not be read.
Before you call either
Epidemic Sound MCP Server
- If you connect from Claude Code or your own client, use an MCP Server API key from Account > API keys, not a Developer Portal key
- Before you download, confirm the user has an active paid plan. A free account only searches and previews
- For a reference song, call SearchExternalReferences first and pass the Spotify ID to SearchRecordings as
externalID - Use an API key for track adaptation. OAuth connections may lack PollEditRecordingJob, which DownloadRecordingEdit needs
- Tell the user that only content published while the subscription is active stays cleared
Slipstream
- Expect a 401 and a browser OAuth sign-in on the first call, even for search, and ask the user to sign in with an active Slipstream subscription
- Call
prepare_licenseuntil it returnsready: true, show the user the one-lineconfirm, and callgenerate_licenseonce with the same values after they agree, since it mints a contract number - Treat
get_track_download_urlas a download only, not a licence, and remember the link spends the partner's download quota when opened - Poll
create_track_clip,extend_trackandrender_soundtrackwith identical arguments untilready: true, and keep callingget_compliance_resultwhile AudioVerify returnstimeout - Take filter values from
get_search_filtersorget_sfx_filters, because unknown values are dropped and an empty match retries without filters, reported inrelaxed_filters
Questions
Which is better for AI agents, Epidemic Sound MCP Server or Slipstream?
Slipstream scores 50 (D) on agent readiness against Epidemic Sound MCP Server's 24.5 (F), and leads in 6 of 7 scored categories. Epidemic Sound MCP Server leads on maintenance & community.
Do Epidemic Sound MCP Server and Slipstream need an API key?
Epidemic Sound MCP Server takes an API key or an OAuth sign-in. Slipstream uses an OAuth sign-in.
Can an agent call Epidemic Sound MCP Server and Slipstream without installing anything?
Yes. Epidemic Sound MCP Server has a hosted endpoint at https://www.epidemicsound.com/a/mcp-service/mcp and Slipstream at https://mcp.slipstreammusic.com/mcp.
Other comparisons with Epidemic Sound MCP Server or Slipstream
- Artyfile Music Licensing vs Epidemic Sound MCP Server
- Artyfile Music Licensing vs Slipstream
- Epidemic Sound MCP Server vs Free Music Library MCP
- Epidemic Sound MCP Server vs Lots of Sounds
- Epidemic Sound MCP Server vs The Rights Foundry
- Free Music Library MCP vs Slipstream
- Lots of Sounds vs Slipstream
- Slipstream vs The Rights Foundry
- Epidemic Sound MCP Server vs LGDA Autonomic Pacing Node
- LGDA Autonomic Pacing Node vs Slipstream
Machine-readable
- This page as Markdown
/compare/epidemic-sound-vs-slipstream.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/epidemic-sound.json·/api/v1/tools/slipstream.json - From a terminal
anchor compare epidemic-sound slipstream(the CLI) - Over MCP
compare_tools {"a": "epidemic-sound", "b": "slipstream"}at/mcp, no key