media-gen
Related Servers
Alternatives to media-gen
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceRender HTML/CSS/JS/SVG animations into high-quality MP4 videos. Exposes render tools to AI agents using Playwright (Chromium) and FFmpeg, running locally or remote.22MIT
- AlicenseAqualityBmaintenanceRenders videos written as web pages (HTML, CSS, JavaScript) to MP4 on an NVIDIA GPU or any CPU. Agents can render a video, preview individual frames as images, and run automatic checks on every frame before delivering.3298 npm3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLets AI agents generate images and videos through a self-hosted studio connected to the user's own fal.ai, Kie.ai or Higgsfield API keys, with tools for exploring models, submitting image and video jobs, waiting on results and importing media from URLs. Runs over HTTP with bearer-token authentication, so agents such as Claude Code, Codex, Cursor or Claude Desktop can create and retrieve media while provider keys stay encrypted server-side.1MIT
- AlicenseAqualityDmaintenanceRender HTML/CSS to PNG/JPG/WebP directly from Claude Desktop, Claude Code, Cursor, or any MCP-compatible client.248 npmMIT

distribea-mcpofficial
AlicenseNot gradedqualityCmaintenanceGenerates images, video, music, and voice from plain-language prompts, shipping them production-ready as optimised WebP with SEO alt text, directly in your terminal or AI agent.64 npm1MIT
keyline-mcpofficial
FlicenseNot gradedqualityBmaintenanceEnables AI agents to author designs as structured JSON scenes and render them to PNG, JPEG, WebP, vector PDF, animated PNG, GIF, MP4 or WebM at every target size, using one native binary with no browser or headless Chrome.6-
TDQS
Scored across 3 tools
The three tools have distinct purposes: render_image produces static images, render_video produces animated video, and list_providers enumerates backend providers. There is no overlap or ambiguity between them.
Tool names follow a consistent snake_case verb_noun convention: render_image, render_video, list_providers. The verb precisely indicates the action and the noun indicates the output or resource, making the pattern predictable.
With exactly three tools, this server is tightly scoped to its media generation purpose and carries no redundant tools. Each tool earns a clear place in the set.
The server covers the apparent core workflow: discover available providers, render static visual assets, and render animated video assets. Since rendering is a stateless generate-to-file operation, no update/delete/list-generated-files tools are required for the declared scope.