Head to head · Music search · October 2026 research run

Epidemic Sound MCP Server vs Lots of Sounds

Lots of Sounds scores 52.9 (D) on agent readiness against Epidemic Sound MCP Server's 24.5 (F), and leads in every scored category. Both do music search.

Best music and sound libraries for AI agents · All 21 music libraries comparisons

Which one, for what

Epidemic Sound MCP Server F

Best for An agent soundtracking video for a person who already pays for Epidemic Sound.

Also in its favour

  • No incidents deducted, where Lots of Sounds loses 3 points for them

Watch for

Labelled beta, with rate limits stated as unpublished and no status page or changelog found

Lots of Sounds D

Best for An agent that needs short CC0 sound effects, ambience or loops with trim points and loudness for video, apps or games.

Ahead on

  • Reliability, 40 against 5
  • Schema & documentation, 79 against 29
  • Agent ergonomics, 88 against 35
  • Security & auth, 46 against 28
  • Payments & pricing, 25 against 15
  • Maintenance & community, 66 against 40
  • Transparency & trust, 43 against 32

Watch for

No page says where the CC0 sounds come from or who recorded them, and the licence page leaves checking suitability to the user

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.

Agent ergonomics Lots of Sounds +53

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.

Lots of Sounds 88

Five compact tools, about 5,000 characters of definitions (25). Search takes page and limit (up to 100), category, tags, duration bounds and sort, and returns total and totalPages (20). Errors are documented with a status, a meaning and an action, and 429 carries a reset time, though MCP error shapes were not seen because no tool was called (15 of 20). Every tool carries readOnlyHint, destructiveHint and idempotentHint, the reads are idempotent, and download_sound is marked non-destructive (20). Defaults on every optional parameter and one required field at most. The npm CLI and examples in JavaScript and Python exist, but the TypeScript client was not found on npm, so there is one published package (8 of 15). 25 + 20 + 15 + 20 + 8 = 88.

Schema & documentation Lots of Sounds +50

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.

Lots of Sounds 79

Public OpenAPI 3.1 spec with 7 operations, and typed JSON Schema inputs on all 5 MCP tools, read with one tools/list (25). llms.txt and llms-full.txt, plus a Copy Markdown option on each docs page (10). Tool descriptions say how search matches, when to call download_sound and that get_profile is only for identifying the account, with fewer when-not-to-use lines in the spec (14 of 20). Enums for category, sort and order, minimum and maximum on limit and page, required ids, and additionalProperties: false on every tool. Duration filters have no bounds (13 of 15). Examples in curl, JavaScript and Python and an error table with actions, but the spec's error schema is a single error string and the coded errors (plan_required, rate_limited) are documented for the CLI only (12 of 15). Paths are versioned /api/v1 and the spec is 1.0.0, but the one dated changelog post is from March 2026 (5 of 15). The spec says 12,000+ sounds where llms.txt says 16,874, and tags use OR on the sample endpoint and AND on search. 25 + 10 + 14 + 13 + 12 + 5 = 79.

Reliability Lots of Sounds +35

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.

Lots of Sounds 40

Graded on the hosted MCP server and the REST API beneath it. No status page found, only the words 'API status: operational' on the home page with no link (0). No readable incident history (5). Daily limits published with numbers, 2,500 for Pro and 50,000 for Enterprise, resetting at midnight UTC (15). The API reference documents 429 with X-RateLimit-Reset and asks for bounded exponential backoff on 429 and 5xx, and every call is a read (15). The home page claims a 99.9% uptime SLA, but the terms of 1 April 2026 say the service is as-is and availability isn't guaranteed, and no SLA document was found (0). Nothing is labelled beta and the registry entry is version 1.0.0, but the public roadmap still lists the MCP server as in progress (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40.

Maintenance & community Lots of Sounds +26

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.

Lots of Sounds 66

Closed service. The npm CLI 0.1.0 was published on 29 October 2026, 24 days ago (30). In the last 90 days the examples repository changed on 26 August and 21 September, the registry entry and TypeScript client appeared on 21 September, the privacy policy took effect on 19 October and the CLI shipped on 29 October, but none of these is a dated changelog entry (10 of 20). The blog's only changelog is March 2026, the roadmap lists a shipped MCP server as in progress, and support is team@lotsofsounds.com with a reply within one business day stated on the pricing page and a UserJot feedback board (6 of 15, closed-service reading). Listed in the official MCP registry as com.lotsofsounds/mcp, a reverse-DNS namespace on its own domain (15). The CLI has no install scripts and the TypeScript client has CI, but the CLI's source repository named on npm isn't public (5 of 10). 30 + 10 + 6 + 15 + 5 = 66.

Security & auth Lots of Sounds +18

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.

Lots of Sounds 46

A plain API key in the x-api-key header, up to 2 on Pro and 20 on Enterprise, made in the dashboard. No scopes, expiry or rotation were documented. The OpenAI endpoint uses OAuth through clerk.lotsofsounds.com with identity scopes only (openid, profile, email), and no key travels in a query string (20 of 30). The whole surface is read-only, with nothing to delete or buy through the API (15 of 20). Results carry catalogue names, descriptions and tags written by the service, with no injection guidance found (8 of 15). Rate limit headers on each response and a statement in the privacy policy that API and MCP use is logged, with no per-call log for the operator found (3 of 15). security.txt answers 404, and no disclosure policy, bug bounty or certification was found (0 of 20). 20 + 15 + 8 + 3 + 0 = 46.

Transparency & trust Lots of Sounds +11

Epidemic Sound MCP Server 32

Closed service under an MCP Server Software License Agreement that the docs link but our reader couldn't render. The music licence itself is stated plainly on the plan pages, cleared forever for content published during an active subscription and not after (10). The privacy policy and legal pages are drawn by script and weren't readable, so no data-handling statement was checked (0). No deprecation policy or dated notice found. The registry's endpoint moved from /a/mcp-server/mcp to /a/mcp-service/mcp with no notice found (0). The REST API docs say its servers are in Europe with audio on Fastly's CDN. Nothing equivalent for the MCP server, and no subprocessor list read (5). 10 + 0 + 0 + 5 = 15.

Lots of Sounds 43

Closed service with terms of 1 April 2026 and a licence page that put every sound under CC0 1.0. No page read says where the sounds come from, who recorded them or how their CC0 status was checked. Sound ids carry an fs- prefix, sound pages show added dates from 2017, and the roadmap plans generated sounds, so the licence's basis can't be traced (10 of 30). The privacy policy of 19 October 2026 lists what is collected, including search terms, and says data is kept 'as long as reasonably necessary', with no periods, DPA or deletion route beyond an email (10 of 30). No deprecation policy or dated notices (0 of 20). Processors are named by type only (hosting, authentication, payments), with no list or locations (3 of 20). 10 + 10 + 0 + 3 = 23.

Score by category

CategoryWeightEpidemic Sound MCP ServerLots of SoundsEdge
Reliability16%540Lots of Sounds +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2979Lots of Sounds +50
Agent ergonomics13%3588Lots of Sounds +53
Security & auth14%2846Lots of Sounds +18
Payments & pricing10%1525Lots of Sounds +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4066Lots of Sounds +26
Transparency & trust7%3243Lots of Sounds +11
Negative events≤150-3
TotalF 24.5/100D 52.9/100

Facts side by side

FactEpidemic Sound MCP ServerLots of Sounds
KindMCP serverMCP server
VendorEpidemic SoundLots of Sounds (Elliott Labs)
Hosted endpointhttps://www.epidemicsound.com/a/mcp-service/mcphttps://api.lotsofsounds.com/mcp
TransportsStreamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingYour planFreemium
x402nono
Tools exposed165
Read-only variant documentednoyes
llms.txtyesyes
MCP registrycom.epidemicsound/mcp-servercom.lotsofsounds/mcp
Last release2026-08-172026-10-29
Terms last updatedcouldn't be read2026-04-01
Privacy policy last updatedcouldn't be read2026-10-19
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text

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.

Lots of Sounds

A small, read-only MCP server and REST API with typed inputs, tool annotations, numbered daily limits and timing and loudness data on each sound. API access needs a person to sign up and subscribe, no page says where the CC0 sounds come from, and the home page's brand logos and uptime SLA have nothing behind them.

Before you call either

Epidemic Sound MCP Server

  1. 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
  2. Before you download, confirm the user has an active paid plan. A free account only searches and previews
  3. For a reference song, call SearchExternalReferences first and pass the Spotify ID to SearchRecordings as externalID
  4. Use an API key for track adaptation. OAuth connections may lack PollEditRecordingJob, which DownloadRecordingEdit needs
  5. Tell the user that only content published while the subscription is active stays cleared

Lots of Sounds

  1. Send short keywords in q, because every word must match a name, description or tag and search isn't semantic
  2. Call download_sound only when the user is ready, because the signed URL expires after one hour
  3. If the server returns 429, wait for X-RateLimit-Reset, which falls at midnight UTC for the daily limit
  4. Pass one or two tags on search_sounds, since tags match with AND logic there and with OR logic on the sample endpoint
  5. Tell the user the source of each sound isn't stated before they use it in a product where provenance matters

Questions

Which is better for AI agents, Epidemic Sound MCP Server or Lots of Sounds?

Lots of Sounds scores 52.9 (D) on agent readiness against Epidemic Sound MCP Server's 24.5 (F), and leads in every scored category.

Do Epidemic Sound MCP Server and Lots of Sounds need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Epidemic Sound MCP Server and Lots of Sounds without installing anything?

Yes. Epidemic Sound MCP Server has a hosted endpoint at https://www.epidemicsound.com/a/mcp-service/mcp and Lots of Sounds at https://api.lotsofsounds.com/mcp.

Other comparisons with Epidemic Sound MCP Server or Lots of Sounds

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.