demoreel MCP server
Related Servers
Alternatives to demoreel MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to drive a self-hosted video toolkit through MCP tools, including lipsync, face restoration, ffmpeg operations, and metadata retrieval.1Do What The F*ck You Want To Public
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform deterministic video editing operations like trim, resize, add text, and more using MCP tools.5 npm5MIT
- AlicenseBqualityCmaintenanceEnables AI agents to programmatically edit videos via FFmpeg, providing tools for probing, trimming, concatenating, timeline composition, LUT generation/application, rendering, and edit verification over MCP.162MIT
- AlicenseAqualityCmaintenanceMCP tools for video transcoding, document conversion, and multi-step pipelines — callable by any AI agent.1260 npm1MIT
- FlicenseAqualityBmaintenanceEnables AI agents to generate videos from text prompts, monitor job status, retrieve completed videos, and cancel ongoing generation tasks through stdio-based MCP tools.4-
- AlicenseAqualityDmaintenanceEnables AI assistants to query the FACEIT platform for players, matches, hubs, and tournaments through typed MCP tools generated from the FACEIT Data API v4.64MIT
TDQS
Scored across 30 tools
Most tools map to clearly distinct resources or actions: matches, rounds, kills, highlights, players, jobs, renders, imports and analytics. A few pairs such as get_player_stats vs get_player_profile and get_feed vs list_highlights need the descriptions to separate them, but the boundaries are still workable.
The tool set uses a consistent snake_case verb_noun pattern throughout: list_matches, get_match, create_highlight, render_reel, import_demo, get_player_profile, and so on. Minor variations like set_featured and produce_match still fit the same predictable convention.
Thirty tools is heavy for an agent-facing surface, even though the server spans demo import, analysis, highlight editing, rendering, jobs and community analytics. Many related operations could be consolidated or grouped, and the size increases selection burden.
The surface covers the domain well: importing demos and source matches, match/round/kill/player analysis, highlight CRUD, featured curation, rendering, job status, feeds, trophies, rivalries and chat rankings. Minor gaps remain, such as no direct upload tool, no match deletion/metadata management, and limited source administration.