MCP Server SimpleNGAT
Related Servers
Alternatives to MCP Server SimpleNGAT
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes video generation and editing tools to MCP-capable clients, enabling text-to-video, image-to-video, video editing, reusable voice and character profiles, and task status queries through natural language.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to generate and upscale AI images, videos, music, and sound effects, manage generation jobs, access model catalogs, and track credits.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients like Claude and ChatGPT to generate images and videos, animate images, create lip-synced videos, list TTS voices, and manage media via remote MCP tools.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to generate professional storyboards and videos from scripts or creative descriptions via MCP-compatible clients.25 npmMIT
- FlicenseNot gradedqualityBmaintenanceProvides an MCP interface to a unified image generation gateway, enabling AI agents to generate images through multiple free and low-cost providers, list sessions and history, and manage provider configurations.-
- AlicenseNot gradedqualityBmaintenanceEnables image and video generation and editing through MCP tools, including image editing, upscaling, background removal, video generation, image-to-video, and video extension. Video generation runs asynchronously with job status and result retrieval.MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: image generation, user info, voice listing, video status polling, video submission, image upscaling, deletion of upscaled files, and health checks. No overlaps or ambiguity exist, so an agent can select the correct tool without confusion.
Tools follow a consistent 'simplengat_verb_noun' pattern (e.g., generate_image, list_voices, generate_video, upscale_image). Minor deviations include 'user_me' (odd phrasing) and 'video_status' (noun-noun rather than verb-noun), but the overall pattern is predictable and readable.
With 8 tools, the server is well-scoped for a media generation service. Each tool covers a distinct operation (generate, upscale, delete, status, user, health, voices), and the count is within the ideal 3-15 range, giving agents sufficient functionality without bloat.
The tool surface covers the full image generation lifecycle (generate, upscale, delete upscaled) and video lifecycle (generate, status, list voices), plus user info and health checks. Minor gaps like video cancellation or image deletion for non-upscaled files are not critical, but the core workflows are well-covered.