Skip to main content

Loom

Loom is a video messaging platform for screen recordings that helps teams communicate asynchronously.

Tools​

The connector exposes five tools, three read-only and two that modify recordings.

ToolRisk
List Recorded Videoslow
Get Videolow
Get Video Transcriptlow
Edit Videomedium
Merge Videosmedium

Get Video Transcript is the tool most likely to pull sensitive content into a prompt, since transcripts carry whatever was said on the recording. It is scored low because the operation itself is a read, not because the content is necessarily safe.

Add the connector​

  1. Open Build > MCP Servers.
  2. Select Add MCP Server.
  3. Find Loom in the catalog, then select Use.
  4. Review the tools and their risk bands. Tools above the selected risk level are left disabled.
  5. Select Create.

Willow opens the new server's edit page with the status draft.

Authentication​

Open the Setup tab on the new server to configure authentication. The tab shows the modes this connector supports and the fields each one needs, so use it as the source of truth rather than guessing which credentials to gather in advance.

For what each mode does and what it forwards to the upstream server, see Configure MCP Server Authentication. Consult Loom's own API documentation for how to issue the credentials it asks for.

Loom has no open public API

Loom's own support documentation says Loom does not offer an open API, and this connector calls https://api.loom.com/v1 with OAuth through the Loom Developer Portal. If Connect ends on a Loom "page doesn't exist" error, nothing in the Setup tab will fix it. To give agents access to Loom recordings, transcripts, and comments, use Atlassian's remote MCP server (https://mcp.atlassian.com/v2/mcp) instead. It includes Loom tools in its READ_LOOM and WRITE_LOOM permission groups, for Loom workspaces linked to an Atlassian Cloud site. Add it as a custom MCP server.

Next steps​

On this page