01 · Records and state owned
Record SDK applications, browser recording sessions and lifecycle events, completed-video share URLs, and oEmbed metadata and player HTML.
Loom
Loom
A category-defining asynchronous video tool with developer APIs and embeddable content, useful for customer-owned review, enablement, support, and personalized communication surfaces.
Media generation, video & localizationSystem of productionExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Receive recording-start, completion, cancellation and insert events, then use the completed share URL to fetch oEmbed metadata and Loom player HTML.
03 · Actions and write paths
Launch and configure the browser recording flow, create a Loom recording through the user-driven SDK experience, and insert its share link or embedded player into the host application.
04 · Authentication and permissions
Record SDK setup uses a public app ID and registered domains; Standard provides separate sandbox and live apps, and optional key-pair authentication adds server-side setup.
05 · Monitoring, approval, and recovery
Protect recording consent, workspace visibility, link sharing, transcript/content sensitivity, retention, and external embedding behavior.
06 · Limits and caveats
Record SDK is browser-only, does not support server-side rendering, and depends on MediaRecorder plus third-party cookies, so compatibility must be checked before setup.
Agent access
MCP support
No official MCP server located
Support: No official MCP server located
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Loom ships them.
Single-platform patterns
- Customer-video review and response workspace
- Media production console
- Localization and variant studio
- Review-and-approval queue
Multi-platform compositions
- Loom + publishing or campaign platform: media production console
- Loom + DAM or CMS + social or video distribution system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
Developer docsRepresentative source
https://dev.loom.com/docs/record-sdk/getting-started ↗First-party developer platform introduction.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Recorded first-party developer source; summary not endpoint-exhaustive
Developer docsSource inventory
https://dev.loom.com/ ↗First-party developer documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://dev.loom.com/docs/embed-sdk/getting-started ↗Documents oEmbed-based embedding.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
HomepageSource inventory
https://www.loom.com/ ↗Product overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP / agent-role validationTargeted review
https://jira.atlassian.com/browse/LOOM-690 ↗Atlassian’s public issue tracker contains a request for a Loom MCP server, indicating that a Loom-specific first-party provider was not yet generally available.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role claim review; exact live reachability was not independently retested for every URL.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.