Setup
Troubleshooting: it won't connect
The five things that actually go wrong, in order of likelihood.
1. Is Editz actually running?
The bridge only exists while npx @editz/editz is running in a terminal. Closed the tab? It's gone. Check for "Editz is running at http://localhost:4103" in that terminal.
2. Are you signed in?
The bridge starts locked. Every tool call gets refused with a "🔒 Editz is locked" message until you sign in with Google in the web editor tab.
3. Missing ffmpeg or python3
Editz prints exactly what's missing and how to install it (e.g. brew install ffmpeg on macOS, sudo apt install ffmpeg on Ubuntu/Debian) — read that message before assuming it's an MCP config problem.
4. Port 9317 already in use
If something else is already listening on 9317, the bridge can't start. Quit whatever else is using that port, or check your terminal output for the actual error.
5. Wrong URL in your agent's config
It's always http://127.0.0.1:9317/mcp — note the trailing /mcp. A common typo is leaving it off.