Loom Advisor
Provides tools for managing Loom screen recordings, including listing, retrieving, editing (trimming/extracting clips), and merging videos.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Loom Advisor list my recent Loom videos"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: Loom Transcript MCP
Installation
pip install m2ai-mcp-loom-advisorConfiguration
Required environment variables:
Variable | Description |
| OAuth2 access token for Loom API |
Optional environment variables:
Variable | Description | Default |
| Loom API base URL |
|
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-missingCode Quality
# Format and lint
ruff check src tests
ruff format src tests
# Type checking
mypy srcProject 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.exampleLicense
MIT
Generated by GRIMLOCK MCP Factory
Available Tools
4 toolsedit_videoB
Edit a video by adding clips or trimming sections. Supports trimming start/end, extracting clips, and updating metadata like title and description.
Inputs: video_id (required), editing_details (required).
get_videoA
Retrieve a specific video by ID. Returns full video details including title, description, duration, embed URL, share link, and transcript availability.
Inputs: video_id (required).
list_recorded_videosA
Retrieve a list of recorded videos from Loom. Returns video metadata including IDs, titles, thumbnails, and creation dates. Supports pagination and folder filtering.
Inputs: limit, offset, folder_id.
merge_videosA
Combine multiple videos into one merged video. Provide at least 2 video IDs in the desired merge order. Optionally specify a title for the merged result.
Inputs: video_ids (required), title.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: editing, retrieving by ID, listing, and merging videos. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern (edit_video, get_video, list_recorded_videos, merge_videos) with predictable structure.
4 tools is a reasonable number for a video management server, covering core operations. It is slightly on the smaller side but not insufficient.
The tool set covers listing, retrieval, editing (including metadata), and merging, but lacks a delete tool, which is a notable gap for full lifecycle management.
Related MCP Connectors
Generate, edit, and render videos via the Shotstack video editing API.
Read and write your Teleprompter.com scripts and folders: list, create, update, and organize.
Create, read, update and publish hosted SlideWeave presentations written in SlideLang.
Manage videos and live streams, inspect captions, players and webhooks, and read play analytics.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive tools for interacting with the Shortcut API, enabling developers to manage stories, comments, projects, and analyze Loom videos for debugging insights.17 npmISC
- FlicenseBqualityNot gradedmaintenanceEnables users to fetch transcripts and comments from public Loom video URLs. It provides tools to retrieve video text data and discussion threads directly through the Model Context Protocol.2-
- AlicenseAqualityCmaintenanceMCP server that exposes 59 tools for Loom's internal GraphQL API, enabling listing, searching, and managing Loom videos, transcripts, comments, tasks, and more.6013MIT
- FlicenseNot gradedqualityNot gradedmaintenanceExtracts transcripts, titles, descriptions, and comments from Loom videos via a remote MCP server.-