Head to head · Music search · October 2026 research run
Free Music Library MCP vs Slipstream
Free Music Library MCP scores 52.4 (D) on agent readiness against Slipstream's 50 (D), and leads in 4 of 7 scored categories. Slipstream leads on reliability. 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 finding free background music, loops or sound effects for a video, podcast or game, with attribution it can hand to the user.
Ahead on
- Schema & documentation, 65 against 50
- Agent ergonomics, 82 against 60
- Payments & pricing, 90 against 25
- Maintenance & community, 31 against 18
Also in its favour
- No key needed to call it
- Runs on your own machine
- Open source
Watch for
Telemetry is on by default and sends the intent argument verbatim and parent process names, while the README says no user data is collected
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 43
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Free Music Library MCP loses 5 points for them
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.
Payments & pricing Free Music Library MCP +65
Free Music Library MCP 90
Free, self-hosted software under MIT with nothing to buy, read with the self-hosted rule. No payment protocol (0), nothing to price (30), free (30), and three sources work with no signup or key (30). Jamendo and Freesound need the user's own free keys. 0 + 30 + 30 + 30 = 90.
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.
Reliability Slipstream +37
Free Music Library MCP 43
Read on the local-software lines, since the server runs on the user's machine over stdio. Installs from PyPI (free-music-library-mcp) with Python 3.10 or later and 3.10 to 3.13 in the classifiers, and from an npm wrapper that needs uv as well (20). package-checks.yml runs pytest on Python 3.10 to 3.13, an end-to-end job and an npm smoke test on every push to main, and the tests hold 32 test functions. Run results on GitHub couldn't be read on 22 November, so passing on main is unchecked (15 of 25). The issue tracker couldn't be read either. The git history shows two merged pull requests, both the author's (5 of 25, unchecked). Six tags from v0.2.0 (9 August 2026) to v0.4.3 (3 October 2026) but no changelog, and v0.4.3 added a tool in a patch release (3 of 15). Version 0.4.3 with a Development Status 4 Beta classifier (0). 20 + 15 + 5 + 3 + 0 = 43.
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 Free Music Library MCP +22
Free Music Library MCP 82
Five compact tools (search_music, list_sources, skills_list, skill_read, check_for_updates) plus three prompts and skill resources (25). limit up to 50 and a sources filter, with no paging or offset (12). A missing key comes back as a skipped entry with key_required and the variable to set, an upstream failure as reason: error, and an unknown source as a named error, all described in the bundled skill. Clients that support elicitation are asked for a missing key mid-call (16). Every tool carries read_only_hint and idempotent_hint, and a search can be repeated safely (20). Only query is required. One language, Python, with the npm package only a launcher. Tool results can carry an appended upgrade notice once a week when PyPI has a newer version (9 of 15). 25 + 12 + 16 + 20 + 9 = 82.
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.
Schema & documentation Free Music Library MCP +15
Free Music Library MCP 65
Read from music_mcp/server.py in a clone of the repository. Every tool's inputs come from typed Python signatures, so tools/list carries a JSON Schema for each (25). The repository has llms.txt, AGENTS.md and a Markdown error skill, and the docs pages on builditwithai.xyz describe each tool. No llms.txt was found served for the site (6 of 10). The description passed to search_music is one line, but its docstring and the server instructions say when to read the error skill, what sources and intent take and that attribution must be shown verbatim (11 of 20). limit is clamped to 1 to 50 in code but not in the schema, and sources is a free list of strings with no enum (7 of 15). The interpreting-errors skill documents each error shape and its recovery, and three prompts show worked queries. The README's tool table names five tools the server doesn't have (11 of 15). The server reports its version, and releases are tagged, but there is no changelog (5 of 15). 25 + 6 + 11 + 7 + 11 + 5 = 65.
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.
Maintenance & community Free Music Library MCP +13
Free Music Library MCP 31
Version 0.4.3 published to PyPI on 3 October 2026, 50 days before this check, per the PyPI release feed and the v0.4.3 tag (20). Two releases in the last 90 days, 0.4.2 (20 September) and 0.4.3 (3 October) (0). One maintainer, 43 commits from 3 August to 3 October 2026, and no commits since. Issues and pull requests on GitHub couldn't be read on 22 November (3 of 25, unchecked). server.json names io.github.surendranb/music-mcp, but the official registry lists six other io.github.surendranb servers and not this one, and the PyPI package it names (music-mcp) doesn't exist (0). CI, CodeQL, monthly Dependabot, a uv.lock and a current MCP SDK range (mcp>=2.0.0,<3). Run results unread (8 of 10). 20 + 0 + 3 + 0 + 8 = 31.
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.
Score by category
| Category | Weight | Free Music Library MCP | Slipstream | Edge |
|---|---|---|---|---|
| Reliability | 16% | 43 | 80 | Slipstream +37 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 65 | 50 | Free Music Library MCP +15 |
| Agent ergonomics | 13% | 82 | 60 | Free Music Library MCP +22 |
| Security & auth | 14% | 45 | 47 | Slipstream +2 |
| Payments & pricing | 10% | 90 | 25 | Free Music Library MCP +65 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 31 | 18 | Free Music Library MCP +13 |
| Transparency & trust | 7% | 35 | 37 | Slipstream +2 |
| Negative events | ≤15 | -5 | 0 | |
| Total | D 52.4/100 | D 50/100 |
Facts side by side
| Fact | Free Music Library MCP | Slipstream |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | BuildItWithAI Studio (Surendran B.) | Slipstream Music |
| Hosted endpoint | no (local only) | https://mcp.slipstreammusic.com/mcp |
| Transports | stdio | Streamable HTTP |
| Auth | None | OAuth |
| Pricing | Free | subscription |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 5 | 56 |
| Read-only variant documented | no | yes |
| llms.txt | no | no |
| Last release | 2026-10-03 | none |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | no document linked | no document linked |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |
Verdicts
Free Music Library MCP
Five read-only tools search five free music sources and return each track's licence and attribution line, three of them with no key. Telemetry is on by default, sends the model's stated intent verbatim, and the documented MCP_TELEMETRY_OPT_OUT does nothing. The installer and the update notice point to package names nobody has published.
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
Free Music Library MCP
- Set
DO_NOT_TRACK=1orMUSIC_MCP_TELEMETRY=falsein the server's env to stop telemetry.MCP_TELEMETRY_OPT_OUT=1has no effect - Install with
uvx free-music-library-mcprather than the curl installer, which edits every MCP client config it finds - If a result says to run
uvx --refresh music-mcp, useuvx --refresh free-music-library-mcpinstead, sincemusic-mcpis not this package on PyPI - Pass the
attributionstring to the user verbatim, and drop CC BY-NC tracks when the use is commercial - Treat a
skippedentry withkey_requiredas final for that source and search the keyless sources instead of retrying
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, Free Music Library MCP or Slipstream?
Free Music Library MCP scores 52.4 (D) on agent readiness against Slipstream's 50 (D), and leads in 4 of 7 scored categories. Slipstream leads on reliability.
Do Free Music Library MCP and Slipstream need an API key?
Free Music Library MCP needs no key. Slipstream uses an OAuth sign-in.
Can an agent call Free Music Library MCP and Slipstream without installing anything?
Free Music Library MCP runs on your own machine, with no hosted endpoint listed. Slipstream has a hosted endpoint at https://mcp.slipstreammusic.com/mcp.
Are Free Music Library MCP and Slipstream open source?
Free Music Library MCP is open source (MIT). No open-source release is listed for Slipstream.
Other comparisons with Free Music Library MCP or Slipstream
- Artyfile Music Licensing vs Free Music Library MCP
- Artyfile Music Licensing vs Slipstream
- Epidemic Sound MCP Server vs Free Music Library MCP
- Epidemic Sound MCP Server vs Slipstream
- Free Music Library MCP vs Lots of Sounds
- Free Music Library MCP vs The Rights Foundry
- Lots of Sounds vs Slipstream
- Slipstream vs The Rights Foundry
- LGDA Autonomic Pacing Node vs Slipstream
- Free Music Library MCP vs LGDA Autonomic Pacing Node
Machine-readable
- This page as Markdown
/compare/free-music-library-mcp-vs-slipstream.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/free-music-library-mcp.json·/api/v1/tools/slipstream.json - From a terminal
anchor compare free-music-library-mcp slipstream(the CLI) - Over MCP
compare_tools {"a": "free-music-library-mcp", "b": "slipstream"}at/mcp, no key