Tintloom
Related Servers
Alternatives to Tintloom
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude Desktop and Claude Code to generate, revise, and edit images with OpenAI's GPT Image models using your own API key, saving every full-resolution result to a local folder. Supports transparent PNGs, multi-image references, and iterative conversational edits.31MIT
- AlicenseNot gradedqualityCmaintenanceEnables generating and editing images from Claude Code using your own Gemini, OpenAI, or OpenRouter API keys, saving generated files directly into your project.MIT
- AlicenseAqualityDmaintenanceEnables Claude to generate and edit images using OpenAI's GPT Image models, with automatic model selection and local file saving.31MIT
- AlicenseAqualityCmaintenanceEnables Claude to generate and edit images through a live-discovered model catalog, including masked edits and exact output sizes, with browser-based sign-in and cost-annotated saved results. It runs locally over stdio and stores images in a configurable directory.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to generate and edit images using Google Gemini AI.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants such as Claude Desktop, Claude Code, Cursor, and OpenCode to generate new images from text prompts and edit or combine local image files, saving the results to a local folder. Supports model listing with per-image pricing, reference images up to 4, and safe per-session caps on paid calls.518 npmMIT
TDQS
Scored across 9 tools
The main agent-facing tools (generate_image, list_image_providers, get_upload_url) are reasonably distinct, but six tools are explicitly internal image-card helpers that agents should not call directly. Some boundaries are still fuzzy, such as save_mask vs. save_selection and get_generated_image vs. get_layer_set, even though the descriptions clarify them.
All tool names use consistent snake_case with clear verb_noun phrasing (get_*, save_*, generate_image, list_image_providers). There are no mixed naming conventions or vague standalone verbs.
Nine tools is not excessive in raw count, but the surface is inflated by six image-card UI helpers that are not useful for an agent to call directly. The effective agent-facing surface is only about three tools, making the set feel heavier and less focused than it should be.
The core image-generation workflow is well covered: generating, editing, combining, splitting into layers, multi-prompt galleries, provider listing, and local file-path guidance. Minor gaps remain around image history/listing, cancellation, or explicit deletion, but the main lifecycle is usable.