Nano-Banana MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | No | Your Gemini API key from Google AI Studio. Required for image generation and editing capabilities. |
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 |
|---|---|
| configure_gemini_tokenA | Configure your Gemini API token for nano-banana image generation |
| generate_imageA | Generate a NEW image from text prompt. Use this ONLY when creating a completely new image, not when modifying an existing one. |
| edit_imageA | Edit a SPECIFIC existing image file, optionally using additional reference images. Use this when you have the exact file path of an image to modify. |
| get_configuration_statusA | Check if Gemini API token is configured |
| continue_editingA | Continue editing the LAST image that was generated or edited in this session, optionally using additional reference images. Use this for iterative improvements, modifications, or changes to the most recent image. This automatically uses the previous image without needing a file path. |
| get_last_image_infoA | Get information about the last generated/edited image in this session (file path, size, etc.). Use this to check what image is currently available for continue_editing. |
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 6 tools
Every tool has a clearly distinct purpose with no ambiguity. The descriptions explicitly differentiate between generating new images, editing specific files, continuing from the last image, and configuration tasks. The boundaries are well-defined, preventing misselection.
The naming follows a consistent verb_noun pattern throughout (e.g., configure_gemini_token, generate_image, edit_image). The only minor deviation is 'continue_editing' which uses a verb_verb form, but it remains readable and fits the pattern overall.
With 6 tools, the count is well-scoped for an image generation/editing server. Each tool earns its place by covering core operations like generation, editing, configuration, and session management without being excessive or sparse.
The tool set provides complete coverage for the image generation and editing domain. It includes CRUD-like operations (generate, edit, continue editing), configuration management, and status checks, with no obvious gaps that would cause agent failures in typical workflows.