agnes-2.5-flash-mcp
Related Servers
Alternatives to agnes-2.5-flash-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityCmaintenanceGenerate images with OpenAI and Google Gemini directly from any MCP client, saving assets into your project with batch support and explicit file output.241 npmMIT
- AlicenseAqualityAmaintenanceEnables video and image generation from any MCP client, with support for models like Veo 3.1, Grok Imagine, and Nano Banana, including text-to-video, image-to-video, image generation and editing.465 npmMIT
- AlicenseAqualityBmaintenanceImage tools for coding agents: generate from text, edit one reference image, remove backgrounds, upscale 2x, and create reference-based sprite animations. The MCP server, CLI and REST API share one key, credit balance and request history. Needs a DreamLayer API key and paid credits; sprite sheets are beta.777 npmMIT

PopNow MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables ChatGPT, Claude, Cursor, VS Code and other MCP clients to create and edit AI images, videos, songs and voiceovers from plain-language requests, including background removal, upscaling, and effect videos. Connects as a hosted remote server with OAuth 2.1 or API key sign-in, quotes credit prices before generating, and returns results directly in the chat.1MIT- FlicenseAqualityCmaintenanceEnables AI assistants to generate images and videos via the Agnes AI API, supporting text-to-image, image-to-image, and video generation.31-
TDQS
Scored across 4 tools
query_video and generate_image are clearly distinct, but create_video and generate_video describe the same core operation with different execution modes. The descriptions help differentiate them, but an agent could still easily pick the wrong one.
All names follow a snake_case verb_noun pattern, but the verbs are inconsistent: query, generate, create, generate. The create_video vs generate_video pair is especially confusing since they are near-synonyms for the same capability.
Four tools is a reasonable size for an image/video generation server. The only slight issue is that generate_video is a redundant sync variant of create_video, but it serves a compatibility purpose.
The core image generation and video creation lifecycles are covered: generate image, create video asynchronously, query status, and sync wait. Minor gaps like cancellation or image task polling are not blocking for the apparent domain.