Nano Banana MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Can also be set via config file at ~/.config/runapi/config.json |
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 | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| edit_imageC | Create a Nano Banana task on RunAPI (edit image). Returns a task id, status, and output URLs. |
| text_to_imageC | Create a Nano Banana task on RunAPI (text to image). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a nano-banana task. |
| check_pricingC | Look up RunAPI pricing for the nano-banana model line. |
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 5 tools
edit_image and text_to_image are clearly distinct generation modes, and login/check_pricing are unambiguous. get_task is slightly generic given two creation paths, but its polling role is conceptually distinct from creation.
Four tools follow a clean verb_noun pattern (get_task, edit_image, text_to_image, check_pricing). Only 'login' deviates as a bare verb, a minor inconsistency.
Five tools is well-scoped for a model-API wrapper: two generation actions, one status poll, one auth, one pricing lookup. Each earns its place with no filler.
Covers create (both modes), poll, auth, and pricing, which handles the core generation lifecycle. Missing list/cancel-task operations are minor gaps an agent can work around.