Loom
Async video messaging.
Verdict
Common use cases
- Find demo recordings by keyword or date
- Extract action items from standup videos
- Summarize client feedback from recorded calls
- Search transcripts for technical discussions
- Pull video links for onboarding documentation
Integration
- Vendor
- Loom
- Category
- communication
- Auth
- OAUTH2
- Composio slug
loom
Tools
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Loom and click Connect. 3. You'll be redirected to Loom's authorization page where you'll sign in with your workspace account. 4. Grant read access to videos, transcripts, and folder metadata — Switchy won't modify or delete any recordings. 5. Once authorized, return to Switchy and confirm the connection shows as active. 6. Open any Space and type '@Loom' followed by a request like 'find the most recent product demo video' to test the connection. 7. If the MCP responds with video details or a transcript snippet, you're ready to use it across all your Spaces.
What teammates see: by default, memories from Loom are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Find Recent Demos
@Loom search for product demo videos from the last two weeks and list their titles with linksOpen in a Space →
Extract Action Items
@Loom find yesterday's standup video and list all action items or decisions mentioned in the transcriptOpen in a Space →
Summarize Client Call
@Loom get the transcript from the Acme Corp kickoff call and summarize the key requirements they mentionedOpen in a Space →
Search Technical Discussions
@Loom search for videos where we discussed API authentication or OAuth implementation in the last monthOpen in a Space →
Build Onboarding Playlist
@Loom find all videos tagged 'onboarding' or 'training' and create a list with titles and descriptionsOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@loom find all videos I recorded this week about the Q4 roadmap and list them with their view counts
Found 3 videos matching your search: 1. "Q4 Roadmap Overview" (Oct 28) — 47 views, 8:32 duration 2. "Feature Prioritization Discussion" (Oct 30) — 23 views, 5:14 duration 3. "Q4 Timeline & Dependencies" (Nov 1) — 12 views, 6:45 duration All videos are currently shared with the #product-team workspace. The first video has 4 comments, including questions about the launch timeline.
This example assumes OAuth scope includes read access to your video library and metadata. Results depend on your Loom workspace permissions — videos shared outside your org may not appear. View counts update with a delay, so real-time analytics aren't guaranteed.
@loom create a new video folder called 'Customer Onboarding' and move the last 5 videos I recorded into it
Created folder 'Customer Onboarding' in your workspace. Moved 5 videos: - "Welcome & Setup Walkthrough" (Oct 29) - "Dashboard Tour" (Oct 30) - "First Project Setup" (Oct 31) - "Invite Team Members" (Nov 1) - "Billing & Plans Overview" (Nov 2) All videos retained their existing share settings. The folder is visible to anyone with workspace access.
This write operation requires elevated OAuth permissions beyond basic video viewing. The MCP can't record new videos — it only organizes existing content. If your workspace enforces folder naming conventions or approval workflows, this action may fail silently or require admin review.
@loom review all videos tagged 'bug-report' from the last month and summarize the most common issues mentioned
Analyzed 12 videos tagged 'bug-report' (Oct 1 - Nov 1). Most frequently mentioned issues: 1. **Export timeout errors** (mentioned in 7 videos) — users report CSV exports failing after 30 seconds on datasets over 10k rows. 2. **Mobile notification delays** (5 videos) — push notifications arrive 5-15 minutes late on iOS. 3. **Search filter reset** (4 videos) — applied filters clear unexpectedly when switching tabs. Three videos included screen recordings of the export timeout. Two mentioned workarounds (smaller date ranges, API export instead).
This synthesis example pairs Loom's video metadata with AI reasoning to extract patterns. The MCP provides video titles, descriptions, and transcripts (if available) — the AI does the thematic analysis. Accuracy depends on whether videos have transcripts enabled and how clearly issues are verbalized on camera.
Use-case deep-dives
When video walkthroughs replace three Slack threads
A 6-person design team ships mocks in Figma, then spends two hours in Slack clarifying intent. The Loom MCP lets an agent pull recent videos by creator or date, so your standup prompt can surface yesterday's design walkthroughs alongside the Figma links. The win is context: instead of reading 40 messages to understand why a button moved, you watch the 90-second Loom where the designer explains it. This works if your team already records design decisions in Loom—if they don't, the MCP returns empty and you're back to Slack archaeology. OAuth2 means each person's agent sees only their own videos unless workspace sharing is configured. If your design cycle is under 48 hours, this keeps everyone aligned without a meeting.
Pull training videos into support ticket context
A 3-person SaaS support team answers the same setup questions daily. They've recorded 20 Loom walkthroughs covering common workflows, but agents can't reference them when drafting replies. The Loom MCP would let an agent search videos by title or pull the most recent onboarding content, then cite the relevant Loom link in the ticket response. The limitation: with zero tools captured yet, we don't know if search or folder filtering exists—if the MCP only lists all videos chronologically, you're manually tagging each Loom in your prompt. This scenario pays off when your video library is under 50 clips and well-titled. Beyond that, you need metadata the MCP may not expose. If your team sends 10+ onboarding emails a week, test this once the tool list populates.
When you record retros but never rewatch them
A 5-person engineering team records every sprint retro in Loom, then forgets they exist. Three sprints later, someone asks 'didn't we already discuss this?' and no one remembers. The Loom MCP could let an agent pull the last four retro videos and generate a summary of recurring themes—if it exposes video metadata or transcripts. Right now, with no tools documented, the MCP might only return video URLs, which means you still have to watch them manually. This use-case hinges on whether Loom's API surfaces transcripts or timestamps. If it does, the agent can synthesize patterns across retros without replaying 90 minutes of video. If it doesn't, you're better off taking written notes in Notion and skipping the MCP entirely. Worth revisiting once the tool inventory is live.
Frequently asked
What does the Loom MCP do in Switchy?
The Loom MCP lets your AI agents access your team's video library — searching transcripts, fetching metadata, and referencing recordings without leaving the workspace. Agents can pull context from past demos, onboarding videos, or bug reports to answer questions or draft summaries. They can't create or edit videos; this is read-only access to your existing content.
Do I need admin permissions to connect Loom?
No. Any Loom user can connect their own account via OAuth2. The MCP requests read-only scopes for videos you have access to — if your Loom workspace restricts certain folders, the agent won't see them either. Admin approval isn't required unless your IT team enforces OAuth app reviews.
Can the MCP record new Loom videos or edit existing ones?
No. The Loom MCP is read-only. Agents can search transcripts, retrieve video titles and descriptions, and reference timestamps, but they can't upload, delete, trim, or change privacy settings. If you need to create videos, use Loom's desktop or browser app directly.
Why use this instead of just searching Loom myself?
Agents can cross-reference Loom transcripts with Slack threads, GitHub issues, or Notion docs in a single query — something you'd do manually across three tabs. If someone asks 'what did the demo cover about permissions?', the agent pulls the relevant timestamp and summarises it alongside the feature spec from Notion.
Who on the team should connect the Loom account?
Whoever has access to the videos your agents need. If your team shares a Loom workspace, one connection usually covers everyone's content. If videos are siloed by department, connect the account with the broadest permissions. Each connection counts as one integration seat in your Switchy plan.