Loom Advisor
MCP server for Loom video management. Provides tools to list, retrieve, edit, and merge Loom screen recordings.
Features
- list_recorded_videos - Retrieve a list of recorded videos with pagination and folder filtering
- get_video - Get detailed information about a specific video
- edit_video - Edit videos by trimming or extracting clips
- merge_videos - Combine multiple videos into one
Installation
pip install m2ai-mcp-loom-advisor
Configuration
Required environment variables:
| Variable | Description |
|---|---|
LOOM_ACCESS_TOKEN |
OAuth2 access token for Loom API |
Optional environment variables:
| Variable | Description | Default |
|---|---|---|
LOOM_BASE_URL |
Loom API base URL | https://api.loom.com/v1 |
Getting an Access Token
Loom uses OAuth2 for authentication. To obtain an access token:
- Register your application in the Loom Developer Portal
- Implement the OAuth2 authorization flow
- Use the returned access token in your configuration
Note: Loom's public API access may be limited. Enterprise users may have additional API capabilities. Contact Loom for API access details.
Usage with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"loom": {
"command": "loom-advisor",
"env": {
"LOOM_ACCESS_TOKEN": "your-access-token"
}
}
}
}
Or run directly with Python:
{
"mcpServers": {
"loom": {
"command": "python",
"args": ["-m", "loom_mcp.server"],
"env": {
"LOOM_ACCESS_TOKEN": "your-access-token"
}
}
}
}
Tools
list_recorded_videos
Retrieve a list of recorded videos from Loom.
Parameters:
limit(optional): Maximum number of videos to return (1-100, default 50)offset(optional): Pagination offset (default 0)folder_id(optional): Filter videos by folder ID
Example:
{
"limit": 10,
"offset": 0,
"folder_id": "folder-abc"
}
get_video
Retrieve detailed information about a specific video.
Parameters:
video_id(required): Unique identifier for the video
Example:
{
"video_id": "abc123"
}
edit_video
Edit a video by adding clips or trimming sections.
Parameters:
video_id(required): Unique identifier for the videoediting_details(required): Object containing edit instructionstrim_start: Start time in seconds to trim from beginningtrim_end: End time in seconds where video should endclips: List of clip objects withstartandendtimestitle: Optional new title for the edited videodescription: Optional new description
Example:
{
"video_id": "abc123",
"editing_details": {
"trim_start": 5,
"trim_end": 120,
"title": "Edited Demo"
}
}
merge_videos
Combine multiple videos into one merged video.
Parameters:
video_ids(required): List of video IDs to merge (minimum 2, in order)title(optional): Title for the merged video
Example:
{
"video_ids": ["video-1", "video-2", "video-3"],
"title": "Combined Demo"
}
Development
Running Tests
# Activate virtual environment
source venv/bin/activate
# Run tests
pytest
# Run with coverage
pytest --cov=loom_mcp --cov-report=term-missing
Code Quality
# Format and lint
ruff check src tests
ruff format src tests
# Type checking
mypy src
Project Structure
loom-mcp/
├── src/
│ └── loom_mcp/
│ ├── __init__.py
│ ├── server.py # MCP server entry point
│ ├── clients/
│ │ ├── __init__.py
│ │ └── loom.py # Loom API client
│ └── tools/
│ ├── __init__.py
│ ├── list_recorded_videos.py
│ ├── get_video.py
│ ├── edit_video.py
│ └── merge_videos.py
├── tests/
│ ├── __init__.py
│ ├── conftest.py
│ ├── test_loom_client.py
│ ├── test_tools.py
│ └── test_server.py
├── pyproject.toml
├── README.md
└── .env.example
License
MIT
Generated by GRIMLOCK MCP Factory
Metadata
Release files for m2ai-mcp-loom-advisor 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| m2ai_mcp_loom_advisor-1.0.0.tar.gz | 14.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| m2ai_mcp_loom_advisor-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.0 kB
Release files / m2ai_mcp_loom_advisor-1.0.0.tar.gz
| Download URL | m2ai_mcp_loom_advisor-1.0.0.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33425b329fb447e8a6aa428fbe2658a4304cff14686abac0b16692f36030ab53
|
|
BLAKE2b-256 checksum How to use checksums |
e710a52d31204439b6c6e6d005de961a45253e30cffc439862e0de251b58caf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / m2ai_mcp_loom_advisor-1.0.0-py3-none-any.whl
| Download URL | m2ai_mcp_loom_advisor-1.0.0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
78d757d6afa1c8de65f483a7aa155d4aac760efe81b74418222972fc1d9e62dc
|
|
BLAKE2b-256 checksum How to use checksums |
f3098e5f9e7a1a0af79506e2acc978b44f44ffbe3f2f3901e5b9af47b0ceebdb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for m2ai-mcp-loom-advisor 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.