Banana Image MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QINIU_BUCKET | Yes | The name of the Qiniu storage bucket. | |
| GEMINI_API_KEY | Yes | Google Gemini API Key used for generating images. | |
| QINIU_ACCESS_KEY | Yes | AccessKey for Qiniu Cloud storage. | |
| QINIU_CDN_DOMAIN | Yes | The CDN domain for Qiniu Cloud storage (e.g., https://your-cdn-domain.com). | |
| QINIU_SECRET_KEY | Yes | SecretKey for Qiniu Cloud storage. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_blog_coverA | Generate a blog cover image using Google Gemini AI, convert to WebP format, and upload to Qiniu CDN |
| upload_imageA | Upload a local or remote image to Qiniu CDN, convert to WebP format, and return the CDN URL |
| generate_imageA | Generate an image using Google Gemini AI, convert to WebP format, upload to Qiniu CDN, and return the CDN URL |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
generate_blog_cover and generate_image have nearly identical descriptions and purposes—both use Gemini AI, convert to WebP, and upload to Qiniu. An agent cannot determine which to use for creating blog covers versus general images based on the descriptions provided.
All tools follow a consistent verb_noun snake_case pattern (generate_blog_cover, generate_image, upload_image) with clear action-oriented verbs.
Three tools is reasonable for an image generation and CDN upload service, though the functional redundancy between the two generation tools effectively reduces the distinct capability count to two.
The set covers basic generation and upload workflows but lacks lifecycle management operations (delete, list, retrieve metadata). The redundant generation tools suggest an incomplete design rather than comprehensive coverage.