Your whole Loom library, readable by AI.
Teams record a lot in Loom: walkthroughs, standups, demos, decisions. That knowledge sits locked inside hundreds of videos nobody has time to re-watch. The Rubi Loom MCP unlocks it, giving Claude a safe, read-only window into your Loom library. An agent can search videos and pull transcripts, summaries, chapters, and AI-extracted action items, all without anyone exposing Loom credentials in a chat window.
Like every Rubi connector, it is a Model Context Protocol (MCP) server: a gatekeeper between the AI agent and the system that controls exactly what is allowed. We explain that gatekeeper pattern in full in the Rubi Odoo MCP. The defining choice for Loom is restraint: this server only reads.
What the Loom MCP can do.
Ask "what did we decide in last week's planning recording?" and get the answer, the action items, and a link, without scrubbing through the video. The server exposes read tools such as search_videos, get_transcript, and get_summary, plus more for chapters, comments, and meeting tasks. The headline is get_video_details, which returns a video's metadata, transcript, chapters, summary, comments, and tasks in a single call.
Every exposed tool only reads. A full set of write operations is built and ready in the codebase but intentionally left disabled pending a security review. This is a deliberate, conservative posture. The same server can be opened up to writes later, per tool, when the organization is ready.
Two layers of security.
No one hands over a Loom login. The connector uses two separate auth layers. Per-user Microsoft Entra ID identity connects the agent, so each person only ever touches their own Loom data. Separately, each user registers their Loom session through a browser-only step, and that credential lives in Azure Key Vault, never seen by the AI and never shown in the chat. The two layers have different lifetimes, so they refresh independently.
Hundreds of recordings become searchable and quotable in chat, without anyone handing over a Loom login.
Part of a family of connectors.
The Loom MCP shares its security model with the Rubi Odoo MCP and the Rubi 365 MCP. The same gatekeeper approach works for any system with an API, and we build these regularly, with more connectors in development.
Frequently asked questions.
No. The server is read-only today. Write operations exist in the codebase but are disabled pending a security review, and would only ever be enabled per tool, with your sign-off.
No. Your Loom session is registered through a browser-only step and stored in Azure Key Vault. It is never seen by the AI or shown in the chat, and each user only ever accesses their own Loom data.
Search the library by topic, pull a transcript or summary, and extract action items and decisions from a recorded meeting. It turns a pile of recordings into a knowledge source an agent can reason over.