A
licenseA
qualityF
maintenanceCreate AI-powered short-form video clips from YouTube videos using any AI assistant. 9 tools for creating shorts, browsing caption templates, music, gameplay overlays, and meme hooks.
9
143
6
MIT
OpenClip
by app.openclip
Server Details
Turn long videos into short, captioned viral clips from your AI assistant. 28 tools, OAuth.
Ownership verified
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
create_agent1 field changed- removed
Input schema / properties / tracker_modelRemoved value: -{ - "description": "\"grid\" (auto-reframe) or \"speaker\" (speaker tracking; paid plans only). Defaults to grid.", - "type": "string" -}
15 tool updates
- First observed
complete_upload - First observed
create_agent - First observed
create_upload - First observed
get_account - First observed
get_render_status - First observed
get_transcript - First observed
get_usage - First observed
get_video_status - First observed
list_agents - First observed
list_caption_presets - First observed
list_clips - First observed
list_supported_providers - First observed
list_videos - First observed
render_clip - First observed
submit_video
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Turn long videos into AI-curated short clips: caption, reframe, thumbnail, schedule, and publish.
Clip videos into captioned shorts, add captions, and schedule posts from AI agents.
AI video editing + publishing: turn clips into vertical shorts, post to TikTok/Instagram/YouTube.
Turn long videos into viral vertical shorts and publish them to TikTok, Instagram and YouTube.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceTurns long-form videos into short-form clips (TikTok/Reels) by reasoning over word-timestamped transcripts, with silence-aware rendering, STT-based validation, and optional reframing/captions.-
- AlicenseAqualityFmaintenanceTurn YouTube videos into short clips — from Claude, Cursor, or any AI assistant that supports MCP. You give it a YouTube link. It finds the best moments, reframes them for vertical video, adds subtitles, and gives you download links. All from a chat.6702MIT
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Submagic's video editing API for creating viral short-form content with AI captions in 107 languages.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.5/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: upload management (create_upload, complete_upload), video submission (submit_video), status tracking (get_video_status, get_render_status), listing (list_videos, list_clips, list_agents, list_caption_presets, list_supported_providers), rendering (render_clip), agent management (create_agent), and auxiliary (get_account, get_usage, get_transcript). No overlapping functionality.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern: 'create_', 'get_', 'list_', 'submit_', 'render_', and 'complete_'. No mixing of conventions or camelCase.
Tool Count5/5
The set of 15 tools is well-scoped for a video processing service, covering the entire workflow from upload/submit through processing, clip listing, rendering, and account management without unnecessary duplication.
Completeness4/5
The tool surface covers the core lifecycle: upload, submit, process, list clips, render, and manage agents. Minor missing operations like video or agent deletion are not critical for the primary use case of generating viral clips from videos.