A
licenseA
qualityD
maintenanceLocal image processing MCP server providing background removal, stock media search, resize, format conversion, and collage creation.
5
MIT
zhenzhen-nanobanana-mcp
Related Servers
Alternatives to zhenzhen-nanobanana-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA local image-generation MCP server that enables text-to-image, image-to-image, inpainting, vibe transfer, precise reference, image viewing, iterative adjustments, and image metadata extraction using native API parameters with cost approval.131AGPL 3.0
- AlicenseBqualityDmaintenanceA local MCP server for generating and editing images using OpenAI-compatible APIs. It provides text-to-image generation and image editing capabilities with configurable endpoints and saves output directly to local files.2204 npmMIT
- AlicenseAqualityCmaintenanceA local MCP server that provides image processing tools including resizing, cropping, format conversion, compression, rotation, flipping, thumbnailing, watermarking, effects, placeholder generation, and overlaying.12MIT
- AlicenseAqualityAmaintenanceMCP server for generating and editing images using xAI's Grok image model, supporting text prompts, batch generation, local files, and optional proxy configurations.254 npm29MIT
- AlicenseAqualityDmaintenanceMCP server for multi-provider AI image generation (AWS Bedrock, OpenAI, Google Gemini) enabling image generation, transformation, and editing through a unified interface.41MIT
TDQS
A3.6/5.0
Scored across 21 tools
Disambiguation2/5
The set has several overlapping surfaces: plan_ecommerce_images vs plan_ecommerce_design, submit_image_tasks vs generate_images, get_image_tasks vs get_batch_result vs get_ecommerce_design, and legacy plan/export_reference_replica vs newer build/export_validated_reference_replica. Detailed descriptions help, but an agent must still infer which workflow/version is active, making misselection likely.
Naming Consistency4/5
Most tools follow a readable snake_case verb_noun pattern such as submit_image_tasks, get_image_tasks, cancel_image_tasks, and confirm_ecommerce_design. Minor inconsistencies exist in singular/plural usage and in legacy vs validated export names, but the overall convention is predictable.
Tool Count3/5
With 21 tools, the set is borderline heavy and includes parallel legacy/new reference-replica paths plus multiple planning/export variants. The count is defensible for a complex image-generation workflow, but several tools feel like duplicate surface area rather than independently necessary operations.
Completeness4/5
The surface covers the main lifecycle: planning, confirmation, submission, polling/waiting, cancellation, retry, inspection, export, and review. There are minor gaps around unified discovery of all designs/batches and cleanup/delete operations, but core workflows are represented.
Maintenance
ActivityNo data
ResponsivenessSyncing