loom-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_videoA | Read a Loom video's name, owner, duration in seconds, creation date, and description. Accepts an HTTPS share URL or video ID. Returns JSON text; unavailable optional metadata is null. Does not modify the video. |
| get_transcriptA | Read a Loom transcript as JSON text with timestamped segments. Accepts an HTTPS share URL or video ID. Each segment contains timestamp_seconds, text, and speaker (null when unavailable). Reports an error if no transcript is available. Does not generate or modify transcripts. |
| get_framesA | Read still frames at 1–10 timestamps, in input order, scaled to 1280 pixels wide. Accepts an HTTPS Loom share URL or video ID. For every timestamp, returns a text block with seconds and an absolute PNG path, followed by its MCP image content. Files are saved under ~/Library/Caches/loom-mcp/<video_id>/frames/. Downloads and reuses a local MP4 cache. Requires an available MP4 export. Does not modify Loom. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools map to clearly distinct outputs: video metadata, transcript text, and extracted still frames. An agent can easily choose based on the desired artifact, and the descriptions reinforce the boundaries.
All tools follow the same get_<resource> pattern, and the nouns are concrete and predictable. There is no mixing of casing or verb conventions.
Three tools is a well-scoped surface for a read-only Loom integration focused on metadata, transcripts, and frames. Each tool serves a distinct retrieval purpose without unnecessary bulk.
The set covers the core read-only extraction workflows implied by the server, including metadata, transcript, and visual frames. It lacks discovery or listing operations, but since the tools accept share URLs or IDs, this is a minor gap rather than a blocking one.