Openrouter-Nano-banana-assets-generator-MCP
Related Servers
Alternatives to Openrouter-Nano-banana-assets-generator-MCP
No user-submitted related servers found.
Related Servers
- AlicenseDqualityCmaintenanceAn MCP server that allows Claude to use OpenAI's image generation capabilities (gpt-image-1) to create image assets for users, which is particularly useful for game and web development projects.193 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides image generation using Google's Nano Banana Gemini models, with additional tools for background removal, upscaling, and format conversion via deterministic post-processing.1MIT
- AlicenseAqualityCmaintenanceMCP server for AI-powered image generation using Google Gemini Nano Banana models. Enables text-to-image generation, image editing, multi-image combination, and favicon generation directly from your AI coding assistant.249 npmMIT
- AlicenseNot gradedqualityCmaintenanceAI-powered image generation MCP server with 16 specialized tools for generating, editing, analyzing, and processing images using Google's Nano Banana 2 model. Supports custom API endpoints and integrates with AI coding assistants via natural language.67 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AI-powered image generation using OpenAI's gpt-image-1 and gpt-image-2 models with advanced text rendering and native transparency support.20 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides AI image generation and editing capabilities using Google's Gemini 2.5 Flash Image API. It allows users to create new images from text, modify existing files, and perform iterative edits through natural language prompts.6766 npmMIT
TDQS
Scored across 4 tools
generate_asset and generate_asset_pack are clearly differentiated by single versus pack output, while edit_asset targets existing assets. ensure_brand_consistency overlaps thematically with generation features that mention brand consistency, but its analyze-and-refine role is distinct enough to avoid serious confusion.
All tool names follow a consistent verb_noun snake_case pattern: generate_asset, generate_asset_pack, edit_asset, ensure_brand_consistency. There is no mixing of camelCase, vague verbs, or inconsistent styles.
Four tools is well-scoped for an asset generation server: one for single assets, one for packs, one for editing, and one for brand consistency. Each tool covers a distinct, necessary workflow without redundancy or bloat.
The core asset lifecycle is covered: create single, create pack, edit, and enforce brand consistency. There is no explicit read/inspect or delete operation, but those are less central to a generation-focused server and agents can work around them using existing editing capabilities.