gigachat-image-mcp
Related Servers
Alternatives to gigachat-image-mcp
- AlicenseAqualityFmaintenanceEnables interaction with Sber GigaChat API for chat, embeddings, image generation, token counting, balance checks, assistants, and file uploads through natural language tools.870 npmMIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceA private MCP server that lets Claude generate images using Google Gemini/Imagen, exposing a generate_image tool.130 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to generate images using Google's Gemini image generation models.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that bridges ChatGPT Plus/Pro to Claude Code, enabling chat, deep research, and image generation via your own account.90 PyPI51MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that enables Claude to generate images using the OpenAI API.21 npmMIT
- FlicenseNot gradedqualityDmaintenanceRemote MCP server enabling Claude to generate images and videos via the Higgsfield AI API, including photorealistic photos, reference-guided images, and video generation from multiple models.-
- AlicenseNot gradedqualityDmaintenanceMCP server that generates images from text prompts using the Kandinsky AI via official API.6MIT
TDQS
Scored across 2 tools
generate_image creates an image (paid, requires user consent and model choice), while check_image only polls status/token balance (free, no consent needed). The descriptions explicitly cross-reference each other and even warn against using generate_image as a retry mechanism, so an agent cannot confuse them.
Both names follow a clean snake_case verb_noun pattern (generate_image, check_image) with the same noun, which accurately signals that the two tools act on the same resource.
Two tools is thin in absolute terms, but the server's scope is narrow (one image-generation backend with an async polling path), and both tools earn their place. Splitting the synchronous generate step from the free status check is a deliberate and justified design.
The surface covers the full async lifecycle: submit a generation, receive a job_id on timeout, and poll for completion, error, and token spend, plus a fallback listing of recent tasks. Minor gaps remain — no explicit cancel/delete for running jobs or saved files — but agents can work around these.