kenari-media-mcp
Related Servers
Alternatives to kenari-media-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables image, video, and audio generation via Magic Hour's API, including async polling, file uploads, and project downloads.4510Apache 2.0- AlicenseAqualityCmaintenanceEnables text-to-image and text-to-video generation via the Agnes AI API, with support for multiple models, async video generation, and automatic file downloads.61MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to generate images and videos, synthesize speech, clone and design voices, and create related media outputs.549 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients such as Claude Desktop and Cursor to generate images and videos, synthesize speech, clone voices, and design custom voices from descriptive prompts. It supports stdio, REST, and SSE transport modes with configurable API hosts, keys, and local or URL-based resource output.549 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to generate images and videos, synthesize text-to-speech audio, and clone or design custom voices. It also supports flexible output handling (URLs or local files) and multiple transport modes including stdio, REST, and SSE.549 npmMIT
- AlicenseBqualityCmaintenanceEnables any MCP-compatible AI agent to generate videos and images from text or reference frames, chain scenes into seamless multi-scene films with sound and speech, and download finished media with manifests and previews. It also exposes account status, plan limits, history and library management through confirm-gated, safe-by-default operations.1634MIT
TDQS
Scored across 8 tools
Image generation/edit and video create/extend are clearly separated, and each tool has a distinct action. However, get_video_status, wait_for_video, and download_video overlap somewhat: both status tools auto-download and wait_for_video is essentially status polling with a loop, which can cause agent misselection.
All tool names follow a consistent snake_case verb_noun pattern: generate_image, edit_image, create_video, extend_video, download_video, etc. The naming style is uniform and predictable across image and video workflows.
Eight tools is well-scoped for a media generation server covering both images and videos. Each tool maps to a meaningful API operation or workflow helper without unnecessary redundancy.
The core media lifecycle is covered: list models, generate/edit images, create/extend videos, check status, wait, and download results. Minor gaps exist around video cancellation/deletion and explicit image result management, but agents can complete primary workflows without workarounds.