mcp-nano-banana
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | Your Google Gemini API key for image generation |
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_imageA | Generate an image using Google Nano Banana (Gemini) AI model. Can generate from text only, or use one or more reference images (up to 14) to guide generation. |
| generate_faviconsA | Generate a full favicon package from a prompt or an existing image. Creates PNG sizes, a web manifest, and optional README, then writes files and/or a ZIP bundle. |
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 2 tools
The two tools are clearly distinct: generate_image produces a single image from text or references, while generate_favicons creates a package of favicon files. There is no overlap in their purposes, so an agent can easily choose between them.
Both tool names follow the same verb_noun pattern (generate_image, generate_favicons). The naming is perfectly consistent and predictable.
With only 2 tools, the set is on the smaller side, but it is appropriately scoped for a server dedicated to Nano Banana image generation. The two tools cover both general image generation and a specific use case (favicons), so the count feels intentional rather than insufficient.
The tool surface covers the core generation capabilities: text-to-image and image-to-image via references, plus a specialized favicon output. Minor gaps exist (e.g., no explicit editing/upscaling tool, no model listing), but the server's stated purpose is well-served.