Slaycaster/loom-local-mcp-server
3.2
If you are the rightful owner of loom-local-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
The Loom Local MCP Server is designed for extracting key frames from Loom videos or local files to aid in debugging and analysis.
Loom Local MCP Server
MCP server for extracting key frames from Loom videos or local files for debugging analysis.
Quick Start
# Build and start the container
./scripts/setup.sh
Usage
Claude Code Configuration
Add to ~/.claude.json:
{
"mcpServers": {
"loom-agent": {
"command": "docker",
"args": ["exec", "-i", "loom-agent", "python", "-m", "loom_agent"]
}
}
}
Analyzing Loom Videos
In Claude Code, simply mention a Loom URL:
"I'm debugging this issue in auth.py. Here's the Loom showing the bug: https://loom.com/share/abc123"
Claude will automatically extract key frames and analyze them.
Local Video Files
- Drop video in
~/loom-videos/ - Reference by filename:
"Check out the bug in this recording: bug-demo.mp4"
Tool Parameters
| Parameter | Default | Description |
|---|---|---|
source | required | Loom URL or local filename |
threshold | 0.3 | Scene change sensitivity (0.0-1.0). Lower = more frames |
max_frames | 20 | Maximum frames to extract |
Directories
~/loom-videos/- Drop local videos here~/loom-frames/- Extracted frames appear here
Development
# Install dev dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Run server locally (without Docker)
python -m loom_agent