Loom Transcript MCP
Provides tools for fetching transcript text and comments from public Loom video URLs.
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 Transcript MCPget the transcript for https://www.loom.com/share/abc123xyz"
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 Transcript MCP (Fixed)
A working Model Context Protocol (MCP) server for fetching transcripts and comments from Loom videos.
This is a fixed fork of @daanvanhulsen/loom-transcript-mcp that resolves the 400 GraphQL errors caused by recent changes to Loom's API.
What Was Fixed
The original package stopped working due to three critical bugs:
Array vs Object: The original code sent GraphQL requests as an array
[{...}]instead of a plain object{...}, which Loom's API now rejects with a 400 error.Missing Headers: Added proper browser-like headers including
AcceptandUser-Agentto pass Loom's validation.Response Parsing: Fixed response data access from
response.data[0].datatoresponse.data.datato match the correct response format.
Installation
NPX (Recommended)
{
"mcpServers": {
"loom-transcript": {
"command": "npx",
"args": ["-y", "@bstyler/loom-transcript-mcp"]
}
}
}Docker
# Build
cd C:\MCPs\loom-transcript-mcp-fixed
docker build -t loom-transcript-mcp .
# Add to Claude config
{
"mcpServers": {
"loom-transcript": {
"command": "docker",
"args": ["run", "--rm", "-i", "loom-transcript-mcp"]
}
}
}From Source
git clone https://github.com/bStyler/loom-transcript-mcp.git
cd loom-transcript-mcp
npm install
npm run build
node dist/index.jsFeatures
getLoomTranscript: Fetches the transcript text from any public Loom video URL
getLoomComments: Fetches comments from a Loom video URL
Usage
After configuring the MCP server in Claude Desktop, you can use it like this:
Can you get the transcript from this Loom video? https://www.loom.com/share/abc123Development
npm install
npm run build
npm startLicense
MIT
Credits
Original package by @daanvanhulsen
Fixed by @bStyler
Available Tools
2 toolsgetLoomCommentsC
Get comments from a Loom video URL
Inputs: videoUrl (required).
getLoomTranscriptC
Get transcript text from a Loom video URL
Inputs: videoUrl (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves comments and the other retrieves transcript text from a Loom video URL. There is no overlap or ambiguity between them, as they target different data types from the same resource.
Both tools follow a consistent verb_noun pattern with 'get' as the verb and descriptive nouns ('LoomComments', 'LoomTranscript'). The naming is uniform and predictable across the tool set.
With only 2 tools, the server feels thin for a transcript-focused domain, lacking operations like search, update, delete, or other common transcript management functions. This minimal set may limit agent capabilities for comprehensive workflows.
The tool set is severely incomplete for a transcript domain, offering only retrieval functions without create, update, delete, or search capabilities. This creates significant gaps that could lead to agent failures when trying to perform full lifecycle operations.
Related MCP Connectors
Any video URL to LLM-ready transcript. ASR built in, no captions needed. TikTok, X, TED and more.
YouTube for AI agents: transcripts, comments, video stats, channel monitor, Shorts captions.
Transcripts, summaries, chapters and timestamped answers for video links, for AI agents.
YouTube and TikTok transcripts, YouTube search and comments as tools. Runs on Apify.