Claude + Loom: What the Integration Can (and Can't) Do in 2026
No — there’s no Claude Loom connector, no Loom MCP server, and (the part that surprises people) no Loom API to build one on. Neither Loom nor Atlassian has shipped anything Claude-connectable, and Atlassian’s official Remote MCP Server is scoped to Jira and Confluence — no Loom tools as of July 2026. The deeper wall: Atlassian’s own docs state “Loom does not offer a open API at this time”. No REST API for videos, no transcript API, no webhooks. So this isn’t a “waiting on a connector” situation — the plumbing a connector would need doesn’t publicly exist.
Here’s what Loom actually exposes, the one community hack and why to be wary of it, and the workflows that genuinely work around the gap.
What Loom actually exposes to developers
The full sanctioned surface, per dev.loom.com:
- recordSDK and embedSDK — embed Loom recording and playback inside your own web app. Free, real, and useful — but it’s UI embedding, not data access.
- oEmbed endpoint (
https://www.loom.com/v1/oembed) — public metadata for any video URL: title, thumbnail, embed HTML, duration. This is the only Loom data a cloud tool can fetch, and it’s metadata only. - SSO/SCIM provisioning on Business/Enterprise — admin user management, nothing to do with videos.
- Native integrations (Slack, Jira, Confluence, Gmail) — the only sanctioned transport for Loom content into other tools.
What’s missing is everything an AI integration would want: listing your videos, fetching transcripts, getting notified when a recording finishes. Loom’s AI features — transcript editing, filler-word removal, summaries, chapters — live inside Loom and are gated to the Business + AI plan (~$24/user/month).
The one community “integration” — and why it’s a hack
karbassi/mcp-loom (6 stars) wraps Loom’s internal, undocumented GraphQL API in 58 MCP tools — authenticated by pasting your LOOM_COOKIE session cookie into Claude Desktop’s config. Call it what it is: a session-cookie hack against a private API, breakable whenever Loom changes anything, and gray territory under the ToS. Fine for personal tinkering, not something to build a workflow on. (Most other “Loom MCP” search results are unrelated projects that happen to share the name.)
The limits that actually matter
- No API means no integration — for anyone. This isn’t a Claude gap; it’s a Loom gap. Zapier-class tools, agent platforms, and MCP authors all face the same wall. Transcripts are not programmatically retrievable.
- No webhooks means no triggers. Nothing can be notified when you finish a recording or a prospect watches one — except Loom’s own notification emails and its native Slack/Jira/Confluence posts.
- Claude can still discuss a Loom — paste a transcript you copied out of the Loom UI and Claude will summarize or draft follow-ups from it — but that’s copy-paste, and it only happens inside a conversation you start.
- Laptop-bound for anything scheduled. Claude Cowork’s scheduled tasks run on a fixed clock, not on inbox events.
Worth noting if you’re evaluating Loom itself: since the Atlassian migration, Creator Lite seats were discontinued and converted to paid Creator seats, and legacy customers moved to list pricing.
If you want the workflow around Loom to run on its own: Carly
You can’t automate Loom’s insides — but almost everything around a Loom is email, Slack, and CRM, and that layer automates beautifully. Carly is an AI executive assistant built to act on triggers, and these flows use only surfaces that actually exist:
- Paste a Loom link to Carly and she pulls the oEmbed metadata — title, duration, thumbnail — and logs the video into your CRM or deal notes with context on who it went to and why.
- When a prospect watches your video, Loom’s “viewed your video” notification email hits your inbox — Carly picks it up, pings you in Slack, and drafts the follow-up while the interest is warm.
- Use Loom’s native Slack integration as the trigger surface: Loom posts new recordings to a channel; Carly picks them up from Slack and routes, annotates, or logs them.
- Run the send-a-Loom cadence: Carly schedules and drafts the email sequence that carries your Loom links — day-0 send, day-3 nudge, day-7 close attempt. The video stays manual; the distribution doesn’t.
- No-code setup. Describe the workflow in plain English; Carly interviews you and builds it.
- Actually sends — drafts and sends email across Gmail and Outlook, updates your CRM, manages tasks.
- Connects to anything — 200+ native integrations, plus any tool with an API via your own key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude | Carly | |
|---|---|---|
| Official Loom connection | No (none exists — no open API) | No (none exists) — works the surfaces that do |
| Summarize a transcript you paste in | Yes | Yes |
| Pull video metadata from a link | No | Yes (oEmbed) |
| Reacts when a prospect views your video | No | Yes (via Loom’s notification email) |
| Routes new Looms from Slack | No | Yes |
| Runs the follow-up cadence | No | Yes, scheduled and sent |
| Works while laptop is closed | No | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude can think about a Loom you hand it. Carly runs the pipeline the Loom travels through.
Frequently Asked Questions
Does Claude work with Loom?
No. There’s no Claude Loom connector or Loom MCP server, and Atlassian’s Remote MCP Server covers Jira and Confluence only. The root cause is Loom itself: Atlassian’s docs confirm Loom has no open API — no video/transcript endpoints and no webhooks — so there’s nothing official for a connector to call.
Can Claude read Loom transcripts?
Only if you paste one in. Loom transcripts are not programmatically retrievable — there’s no transcript API. Copy the transcript from Loom’s UI into a chat and Claude will happily summarize it or draft the follow-up; it just can’t fetch it itself.
Is there any Loom MCP server?
One community project, karbassi/mcp-loom, wraps Loom’s internal undocumented GraphQL API using your pasted session cookie. It’s unofficial, fragile, and ToS-gray — a hack for tinkering, not an integration to rely on.
How do I automate my Loom follow-up workflow, then?
Automate the layer around the video: Carly logs Loom links with oEmbed metadata, reacts to Loom’s view-notification emails with Slack alerts and drafted follow-ups, picks new recordings off Loom’s native Slack integration, and runs the send cadence in Gmail or Outlook. AI agents start at $35/month.
More: Claude + Zoom · Claude + Slack · Claude + Fathom · Claude connectors · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
