snapgen-mcp
Related Servers
Alternatives to snapgen-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides tools to interact with RunwayML and Luma AI APIs for video and image generation, including text-to-video, image-to-video, prompt enhancement, and management of generations.17ISC
- AlicenseNot gradedqualityCmaintenanceGives AI assistants the ability to generate and iteratively refine images and videos with Google AI Studio models, including image creation/editing, Veo and Omni video generation, and async job tracking. Also lets them analyze existing media and list the models available with their API key.1ISC
- AlicenseAqualityDmaintenanceEnables AI image and video generation using Google Nano Banana and Veo 3.1 via a LiteLLM gateway, providing tools for synchronous image generation and asynchronous video generation with polling, returning public URLs.4MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible agents to access KaiRouter's video generation API, providing tools to list available video models, generate videos (text-to-video or image-to-video) asynchronously, check job status, and list recent jobs.4MIT
- AlicenseAqualityCmaintenanceEnables AI agents to interact with a Stable Diffusion REST API for image generation, inpainting, model management, and merging.18GPL 3.0
- AlicenseBqualityDmaintenanceEnables AI-powered image and video generation through the TensorsLab API using models like SeeDream and SeeDance. It supports tasks such as creating high-resolution media from text prompts, image-to-video conversion, and monitoring generation status.9MIT
TDQS
Scored across 8 tools
The three image generators are distinguished by model (nano-banana vs GPT vs Grok), though the generic name 'generate_image' for nano-banana is slightly misleading next to 'generate_gpt_image'/'generate_grok_image'. get_generation vs wait_for_generation are separable (fetch once vs poll to completion), and snapgen_request is a documented escape hatch, but it technically overlaps with every other tool.
Strong verb_noun pattern throughout (generate_*, get_generation, list_generations, wait_for_generation). The only deviation is snapgen_request, which breaks the verb_noun convention but is still readable and clearly scoped as a fallback.
Eight tools is well within the sweet spot, with generation, polling, retrieval, listing, and a documented catch-all each earning a distinct slot. No redundancy that would justify trimming.
Full lifecycle is covered: submit (generate_image/video), poll (wait_for_generation), fetch (get_generation), and list (list_generations). No delete/cancel operation exists, but snapgen_request provides an escape hatch for uncovered endpoints like cancellation.