The Loom MCP for enriching public Loom links in your workflows
Give it a public Loom share URL and get back the title, thumbnail, duration, dimensions, and the official embed iframe, as a workflow step. No API key, because it uses Loom's public oEmbed endpoint.
What the Loom MCP connector does
The Loom connector for Mattering Automations does one honest thing: it reads Loom's public oEmbed endpoint. Pass it any public Loom share URL and the loom.get_oembed node returns the embeddable iframe HTML, the thumbnail URL and its dimensions, the video width and height, the title, and the duration.
This is the full surface, on purpose. Loom does not offer an open or authenticated REST API, so there is no way to list a workspace's videos, read folders, or manage recordings from an automation. The one public, credential-free endpoint Loom does publish is oEmbed, and that is exactly what this connector wraps.
The node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can call it, alongside Matter, the AI assistant built into the platform. When a workflow or an agent encounters a bare Loom link, it can turn that link into real metadata instead of an opaque URL.
One connection, three surfaces
- Visual automations. Drag Loom nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Loom node, ready to drop on the canvas
1 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 1
Loom: Get Video oEmbed
Fetch oEmbed metadata for a PUBLIC Loom share URL. Returns the embeddable iframe HTML, thumbnail URL and dimensions, video width and height, title, and duration. Public endpoint (no auth). Private or unlisted videos return a 404. Verified live 2026-07-24.
Connecting Loom takes one credential
There is nothing to get. Loom's oEmbed endpoint is public and requires no API key, no OAuth, and no account. Loom does not offer an open API, so no credential exists to request.
In Mattering Automations, open Connectors and add the Loom connector.
There is no credential to enter; Loom oEmbed is a public endpoint.
The Loom: Get Video oEmbed node appears in the canvas palette, ready to use.
Give it a public Loom share URL and run it to confirm the metadata comes back.
Common uses for the Loom MCP
Enrich a Loom link in an agent workflow
When a task, message, or record contains a Loom share URL, resolve it to a real title, thumbnail, and duration so the downstream step can show a proper preview instead of a raw link.
Validate a public share URL
A successful oEmbed response confirms the URL is a public, reachable Loom video; a 404 flags a private, unlisted, or broken link before it reaches your audience.
Build a video card or embed
Use the returned iframe HTML and thumbnail to render a consistent embed in a page, digest, or notification, sized to fit with the optional maxwidth and maxheight parameters.
Log video metadata to a database
Pull the title and duration for each shared Loom and write them into a Mattering database so a table of recordings stays readable, without anyone copying titles by hand.
Example: A shared Loom link becomes a rich preview
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a workflow receives a Loom share URL from an upstream step (a form, a message, or a task field).
Loom: Get Video oEmbed runs against that URL.
A condition checks whether the call succeeded; a 404 means the link is not public.
On success, the title, thumbnail, and duration are written back to the task or posted where the team will see the preview.
Loom MCP questions, answered
Does this connector need a Loom API key?
No. It calls Loom's public oEmbed endpoint, which requires no API key, no OAuth, and no account. You add the connector and use the node directly.
Can it list my Loom videos or read my folders?
No. Loom does not offer an open or authenticated REST API, so there is no way for any tool to list your videos, browse folders, or manage recordings programmatically. This connector only reads public embed metadata for a share URL you already have.
Is the endpoint it uses actually public?
Yes. oEmbed is a standard embed-metadata endpoint, and Loom is a registered oEmbed provider used by tools like WordPress, Embedly, and Iframely. The connector reads that same public endpoint and does not download or scrape the video file itself.
What does the node return?
For a public Loom share URL it returns the embeddable iframe HTML, the thumbnail URL and its width and height, the video width and height, the title, and the duration. You can optionally pass maxwidth and maxheight to constrain the embed size.
What happens with a private or unlisted video?
The endpoint returns a 404 for private, unlisted, or nonexistent videos. The node handles that fail-soft, so your workflow can branch on the failure rather than crash, which makes it a clean way to check whether a link is public.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes the node over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant can use it. Matter, the assistant built into the platform, uses it natively.
Will you add video management once Loom ships an API?
If Loom publishes a real authenticated API, those capabilities can be added as separate nodes then. Today no such API exists, so we do not claim or stub capabilities we cannot actually deliver.
Put Loom to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Loom is a product of its respective owner; Mattering is an independent platform.