rubi.works
Rubi Loom MCP Custom MCP Server · Product & Scope Overview
Your whole Loom library, readable by AI. Transcripts, summaries, and action items, without anyone handing over credentials.

Rubi Loom MCP gives Claude a safe, read-only window into your organization's Loom recordings. Ask for a video and get its transcript; ask what was decided and get the summary, chapters, and action items. The knowledge locked inside hundreds of recordings becomes searchable and quotable in chat. No screen-scraping, no copy-paste, no shared logins.

It is read-only by design: the agent can browse, search, and read, and nothing more. Sign-in runs through Microsoft Entra ID, and every user only ever reaches their own Loom data.

Search the Whole Library

Find the right recording fast. The agent scans your library by keyword, folder, and space the way a person would, then drills into the one that matters.

search_videos list_videos list_folders list_spaces

Read Everything in One Call

One get_video_details call returns metadata, full transcript, chapters, summary, comments, and tasks together. No back-and-forth, no stitching results by hand.

get_video_details get_transcript get_summary get_chapters

Decisions & Action Items

The outcomes of a recorded meeting surface as structured data: extracted tasks with assignee and status, key takeaways, meeting notes, and linked Confluence pages.

get_tasks get_key_takeaways get_meeting_notes get_confluence_pages

Engagement & Context

The agent reads comments, reactions, tags, view and watch stats, and contributor details, so it understands not just what a video says but how the team responded to it.

get_comments get_reactions get_tags get_user

Read-Only by Design

Every exposed tool only reads. A full set of write operations is already built but sits dormant in the codebase, intentionally disabled pending a security review. Writes can be switched on later, per tool, when you are ready.

Read-only tools Writes built, not enabled Per-tool opt-in later

Two-Layer Security Model

Microsoft Entra ID single sign-on gates the connector. Each user then registers their own Loom session through a browser-only step, and that secret lives in Azure Key Vault, never in chat or seen by the AI. The two layers refresh independently, so each person only ever touches their own data.

Microsoft Entra ID SSO Azure Key Vault secrets Per-user scoping
How an org gets it running
1
Deploy the server

We stand up the server on Azure Functions with secrets held in Azure Key Vault. Nothing to install on your side.

2
Wire up Entra ID

Single sign-on is configured against your Microsoft Entra ID so only your people can reach the connector.

3
Connect the connector

Each user clicks Connect once to authorize the connector through Entra ID.

4
Register Loom session

A short browser-only step registers the user's personal Loom session, stored in Key Vault, never pasted in chat.

5
Set the read-only scope

We confirm which read tools are live. Write operations stay disabled until a security review signs off.

6
Start asking

Claude can now search videos, read transcripts and summaries, and pull action items across your library.

What you provide
Microsoft Entra ID tenant

So we can configure single sign-on for your users.

Loom workspace

The library of recordings you want made searchable.

Per-user Loom access

Each user registers their own Loom session through the browser-only step.

Azure subscription

To host the Functions app and Key Vault, or we can host it for you.

Scope notice: This document covers the read-only functionality included in the package. Enabling write operations, such as posting comments or managing videos, folders, and tasks, requires a separate security review and would be scoped and quoted separately. Integrations beyond Loom, Microsoft Entra ID, and the listed Azure services are outside this engagement.

Book Meeting