vimeo-mcp
Related Servers
Alternatives to vimeo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to manage Wistia media, folders, captions, channels, webinars, sharing, analytics, uploads, accounts, and background jobs through 169 stable API tools with guarded writes, bounded paging, and private account handling.16928 npmAGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage videos on PlayVideo, including collections, videos, webhooks, embed settings, API keys, and account management.6 npmMIT

@vidalytics/mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to connect to Vidalytics video analytics and manage videos, stats, audience retention, CTAs, uploads, and more through natural language.29 npmMIT
Descript MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to search and inspect Drives and projects, import media, perform natural-language AI edits to video and audio, publish shareable exports, and export transcripts or editing timelines.37Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manage video projects, write story and brief, convert, estimate costs, propose paid actions, run approved proposals, discard and restore assets.3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage a user's own SmugMug account in plain language — creating and securing galleries, auditing visits, renaming and organizing photos, and applying price lists — without needing a SmugMug API key, OAuth setup, or code.795 PyPIElastic 2.0
TDQS
Scored across 43 tools
Despite 43 tools, each has a crisply distinct target: videos, folders, showcases, chapters, texttracks, comments, embed presets and analytics are cleanly separated, and overloaded pairs are explicitly disambiguated in the descriptions (list_videos vs search_videos, get_video_stats vs get_video_analytics, get_transcript vs list_texttracks). The only mild redundancy is get_video_privacy overlapping the privacy field of get_video, but the dedicated tool adds whitelist detail. An agent should almost never misselect.
Nearly all names follow a strict snake_case verb_noun pattern (list_videos, create_folder, delete_showcase, update_texttrack), which makes the resource+action readable at a glance. Minor deviations like get_me and the singular/plural split between add_video_to_showcase and add_videos_to_folder are too small to break predictability.
43 tools is well past the 25-tool threshold where selection burden becomes real, even allowing for Vimeo's broad API surface. Sub-resources such as chapters and texttracks are each given four to five dedicated tools, and the granularity could be consolidated (e.g. generic sub-resource create/update/delete).
Coverage is genuinely deep: full CRUD for videos, folders, showcases, chapters, texttracks and comments, plus upload, download links, thumbnails, tags, privacy, embed presets, analytics and account introspection. Gaps remain around social/interaction surfaces (likes, ratings, collaborators/credits, live events) and there is no update path for showscases' video ordering beyond sort order. These are workable omissions, not blockers.