MCP Server
Integrate Cloudglue’s powerful video understanding capabilities directly into Claude Desktop, Cursor, and other AI assistants
Quick Start
First, make sure you have a Cloudglue API key to authenticate with the service.
The Cloudglue MCP server lets you connect AI assistants like Claude Desktop and Cursor to Cloudglue’s video understanding capabilities through the Model Context Protocol.
Using the Cloudglue MCP server, you can bring advanced video analysis, transcription, and extraction features directly into your favorite AI chat applications. This allows your AI assistants to understand, analyze, and extract insights from video content without leaving your workflow - whether you’re looking to transcribe meetings, extract structured data from video clips, or have conversations about video collections.
Setup
1. Get API Key
Create a Cloudglue API key from cloudglue.dev. This key will authenticate the MCP server with your Cloudglue account.
2. Configure MCP Client
Configure your MCP client (Claude Desktop or Cursor) to use the Cloudglue MCP server:
Claude Desktop uses a configuration file to manage MCP servers:
- Open the Claude menu on your computer and select “Settings…”
- Click on “Developer” in the left-hand bar of the Settings pane
- Click on “Edit Config”
This will open your claude_desktop_config.json
file (located at ~/Library/Application Support/Claude/claude_desktop_config.json
on macOS or %APPDATA%\Claude\claude_desktop_config.json
on Windows).
Add the following configuration to the file:
Replace <YOUR-API-KEY>
with your Cloudglue API key from step 1.
After updating the configuration, restart Claude Desktop completely.
Claude Desktop uses a configuration file to manage MCP servers:
- Open the Claude menu on your computer and select “Settings…”
- Click on “Developer” in the left-hand bar of the Settings pane
- Click on “Edit Config”
This will open your claude_desktop_config.json
file (located at ~/Library/Application Support/Claude/claude_desktop_config.json
on macOS or %APPDATA%\Claude\claude_desktop_config.json
on Windows).
Add the following configuration to the file:
Replace <YOUR-API-KEY>
with your Cloudglue API key from step 1.
After updating the configuration, restart Claude Desktop completely.
Cursor provides a UI for adding MCP servers (requires Cursor version 0.45.6+):
- Open Cursor Settings
- Go to Features > MCP Servers
- Click ”+ Add new global MCP server”
- Enter the following configuration:
Replace <YOUR-API-KEY>
with your Cloudglue API key from step 1.
Alternatively, you can add a project-specific configuration by creating a .cursor/mcp.json
file in your project directory, or a global configuration by creating a ~/.cursor/mcp.json
file in your home directory.
3. Verify Installation
Once configured:
- In Claude Desktop: You should see a slider icon in the bottom left corner of the input box. Click it to see the available Cloudglue tools.
- In Cursor: The Agent will automatically detect and use relevant Cloudglue tools when needed.
Available Tools
Once configured, your AI assistant can access the following Cloudglue tools:
Chat with Videos
chat_with_video_collection
: Get chat completion responses from your video collections
Transcribe and Extract Information
transcribe_cloudglue_video
: Get rich multimodal transcripts from uploaded videostranscribe_youtube_video
: Get detailed descriptions of YouTube videosextract_cloudglue_video_entities
: Extract detailed entities from uploaded videosextract_youtube_video_entities
: Extract detailed entities from YouTube videos
Manage Videos and Collections
list_videos
: View metadata for all accessible videosget_video_info
: Get information about specific videoslist_video_collections
: View metadata for accessible collectionslist_collection_videos
: View videos in a specific collection
Access Rich Data
get_collection_rich_transcripts
: Get rich transcripts from collection videosget_collection_video_entities
: Get extracted entities from collection videos
Troubleshooting
If the MCP server isn’t working:
- Ensure you have Node.js installed (
node --version
in terminal) - Verify your API key is correct
- Restart the client application completely
- Check logs for any error messages