- Home
- Resources
- Integrations
- Cloudglue
Claude Cloudglue connectorWhat Claude can do in your Cloudglue account.
The Claude Cloudglue connector exposes 10 tools: 6 read, 4 write, 0 undescribed. Six browse and search your video collections; four launch new processing in your Cloudglue account when none exists yet: descriptions, entity extraction, camera shots and chapters. It runs as a Claude Desktop extension.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can work with your Cloudglue videos
Cloudglue turns video into structured data that a language model can use. With the connector, you ask Claude about a whole collection or a single file in plain English: it finds the right videos, reads their summaries, jumps to the moment where something is said or shown, and, when the analysis does not exist yet, asks Cloudglue to produce it.
Get the gist of a collection. A content manager wants to know what a library of webinars covers; retrieve_summaries brings back titles and summaries in bulk.
Find the exact moment. A researcher looks for the passage where a speaker mentions pricing; search_video_moments searches speech, on-screen text and visual descriptions across the collection and returns the matching segments.
Turn a recording into data. An analyst needs every product named in a demo video; extract_video_entities runs an extraction from a precise prompt, and segment_video_chapters splits the video into chapters. Both check for an existing job before creating a new one in your account.
What it will not do: none of the ten documented tools uploads or deletes a video, and nothing runs by itself when a new file lands in a collection. It only acts while it answers you, on the desktop app where the extension is installed. The Integrations hub lists the platforms we document.
Five words before you install
The vocabulary Claude uses around this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work on it while it answers you.
- Tool
- One named thing a connector lets Claude do on that account. Claude picks the ones it needs; the directory sheet lists them by name.
- Authorization
- How you hand Claude the access it uses afterwards; for Cloudglue, an API key entered once, and removable later.
- Approval
- The confirmation Claude waits for before it starts something in your account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Cloudglue.
Connect Cloudglue to Claude in three steps
- 01
Find Cloudglue in your settings
Open Claude Desktop's settings, go to Customize, then Connectors, and look for Cloudglue. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can set it up individually.
- 02
Start the connection
Launch the installation from its row and provide your Cloudglue credentials when asked. If the link breaks later, Disconnect it and set it up again: that usually repairs a broken connection.
- 03
Check what you grant
Read what the service asks for before you validate. The access is defined on Cloudglue's side, not by Claude, and you can withdraw it later from your Cloudglue account, for example by revoking the key you used.
The 10 tools, grouped by what they do
Cloudglue gives Claude 10 tools: 6 that read your account, 4 that change something in it.
Two groups: six tools that browse and search what already exists, and four that launch new processing on a video. Cloudglue describes each one, and the names stay exactly as Claude shows them.
- 6 read
- 4 write
Tools index
What Claude reads (6)
6 toolsSix tools that list, search and read your collections without starting any processing.
list_collections
Shows which video collections exist in your account, with their identifiers, video counts and types. Those identifiers are what the other tools need to work on a collection.
list_videos
Browses and searches video metadata with filters, for instance by date, or shows what sits inside a given collection.
get_video_metadata
Returns the technical profile of one Cloudglue file: duration, resolution, file size, processing status and computed statistics. It is about the file, not about what the video says.
retrieve_summaries
Brings back the summaries and titles of a whole collection in bulk, to grasp its content and themes without opening every video.
search_video_moments
Runs a semantic search inside a collection to locate precise segments, across speech, on-screen text and visual descriptions. Handy when you remember what was said but not in which recording.
search_video_summaries
Finds the most relevant videos of a collection for a topic and returns structured results with video information and relevance scores. It answers which videos, not which minute.
What Claude launches in your account (4)
4 toolsFour tools that produce a new analysis when none exists yet. No source describes a specific confirmation: the general rule below applies.
describe_video
Approval: see the ruleGets a full description of one video, delivered in pages. It checks for an existing description first and only creates a new one when none is found.
extract_video_entities
Approval: see the rulePulls structured entities out of a video from a prompt you write, with the collection as an optional setting. It checks for an existing extraction first and only creates a new one when none exists.
segment_video_camera_shots
Approval: see the ruleSplits a video into camera shots. Cloudglue checks for an existing shot segmentation job first, and only creates a new job when there is none.
segment_video_chapters
Approval: see the ruleCuts a video into chapters. Like the shot tool, it looks for an existing chapter segmentation job before creating a new one in your account.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. Here, four tools can start new processing in your Cloudglue account; the six others only read.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked each time. They can also limit what a connector may do for the whole organization, for example keeping reading and closing writing, and nobody overrides that from their own account. Claude works with the access of the key you provided and nothing beyond it: collections that key cannot reach stay out of the conversation.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that answer is published nowhere: it is a real gap in the catalogue.
What is published is the general rule: desktop extensions such as this one install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organization first. For the current state of this one, check its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing fires when a video is uploaded or finishes processing.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The verification badge is not a security audit, and Anthropic states on every sheet that it does not control which tools a publisher exposes. Only Cloudglue's own repository documents this connector; no Claude help article covers it. To compare with a remote connector, see the Claude adobe-workfront connector.
Need help connecting Cloudglue to Claude?
A person reads every message.