Lots of Sounds
Free plan · From $15/moActively maintained
≈ 308visits/mo
Little sign of use · estimate, read Oct 13, 2026
- For
- developers and product teams adding royalty-free sound effects to apps, games, or AI agents
- Price
- Free plan · From $15/mopricing page, read Oct 17, 2026
- Activity
- Actively maintainedrelease 4 weeks ago
- Runs as
- API
- Used for
- search and stream sound effects through the REST API
- add notification and UI sounds to web apps
- assemble video edits with whooshes, hits and transitions
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantslotsofsounds.com ↗
Free plan · From $15/mo
- MCP servercom.lotsofsounds/mcpverified in the MCP registry
- Stateanswers, 5 toolschecked 2026-10-17
- Address to connectapi.lotsofsounds.com/mcp
- OpenAPI spec7 pathsthe spec ↗
- API docslotsofsounds.com/developersthe vendor's page ↗
- MCP docslotsofsounds.com/docs/mcpthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Lots of Sounds for?
Sign in to leave a noteWhat is Lots of Sounds?
Serves royalty-free CC0 sound effects through a REST API, searchable by keyword, tag and duration, with streamable or downloadable files.
Who is Lots of Sounds for?
developers and product teams adding royalty-free sound effects to apps, games, or AI agents
How much does Lots of Sounds cost?
Lots of Sounds has a free plan; paid plans start at $15/mo, per its pricing page on 2026-10-17.
Is Lots of Sounds free?
Yes, Lots of Sounds has a free plan, per its pricing page on 2026-10-17.
Do people use Lots of Sounds?
Little sign of use: ≈ 308 visits/mo · estimate, 2026-10.
Is Lots of Sounds still maintained?
Actively maintained: release 4 weeks ago.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.