woven-sfx
Sound Effects Library for AI Agents
Open source library of whooshes, pops, and glitches built for agent video edits. Install the skill and MCP server once. Your agent searches the catalog and pulls the right .wav when it needs a sound.
$ npx skills add woven-video/skills --skill add-sfxBrowse by sound
Browse sounds
Preview waveforms and copy sound ids for your agent.
/
No sounds match your search.
Frequently asked questions
- What is Woven SFX?
- Woven SFX is an open-source sound effects registry built for AI agents. It ships a skills.sh installable skill, stdio MCP tools, and a browsable catalog of whooshes, pops, glitches, and other .wav files for video editing workflows.
- How do I install Woven SFX for my AI agent?
- Run: npx skills add woven-video/skills --skill add-sfx and choose your agent, or use --agent codex -y, --agent claude-code -y, or --agent cursor -y for a non-interactive install. Then add the woven-sfx-mcp server to your MCP config and pull sounds with scripts/pull-library.sh or on-demand via sfx_search and sfx_pull.
- What MCP tools does woven-sfx provide?
- Three tools: sfx_search (find sounds by normal words, id, or tag), sfx_pull (download a selected sound by id), and sfx_list_installed (list cached .wav files in your project library).
- Where are sound files stored locally?
- By default in ./sounds/sfx/ under your project root. Override with WOVEN_SFX_LIBRARY or an sfx-library path in .claude/project.md. The MCP server and pull script use the same resolution order.
- How many sounds are in the Woven SFX catalog?
- The catalog at https://www.woven.video/sfx/catalog.json currently lists 35 sounds (catalog v1.0.0), including whooshes, camera shutters, glitches, dings, and impacts. New sounds are added to the open registry over time.
- Is Woven SFX free?
- Yes. The skill, MCP server, and catalog are open source (MIT). Sound files are CC0. Install with npx skills add — no account required.
- What video editing workflows use woven-sfx?
- Agents search the catalog with normal words, choose a sound id, then pull the .wav into the project library. Before assembly or render, they verify cached files with sfx_list_installed and pull any missing ids.