Nano-Banana MCP Server

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.3
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness5/5
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.
Average 3.8/5 across 6 of 6 tools scored. Lowest: 2.9/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool configures an API token, implying a write or setup operation, but does not disclose key behavioral traits such as whether this persists across sessions, requires specific permissions, has side effects (e.g., overwriting existing config), or error handling. This leaves significant gaps for a configuration tool with no annotation support.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence: 'Configure your Gemini API token for nano-banana image generation.' It is front-loaded with the core action and context, with zero wasted words. Every part of the sentence contributes to understanding the tool's purpose, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity as a configuration operation with no annotations and no output schema, the description is incomplete. It does not cover what happens after configuration (e.g., success response, error cases), how it interacts with sibling tools like 'generate_image', or behavioral details. For a tool that likely mutates state or sets up critical API access, more context is needed to be fully helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the 'apiKey' parameter well-documented as 'Your Gemini API key from Google AI Studio.' The description adds no additional parameter semantics beyond this, as it does not explain format, validation, or usage context for the key. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the heavy lifting without extra value from the description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Configure your Gemini API token for nano-banana image generation.' It specifies the verb ('configure') and resource ('Gemini API token'), and mentions the context ('nano-banana image generation'). However, it does not explicitly differentiate from sibling tools like 'get_configuration_status' or 'get_last_image_info', which might be related to configuration or image info, so it misses full sibling distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a token before generating images), exclusions (e.g., not for editing images), or direct alternatives among the sibling tools. The context 'for nano-banana image generation' implies a use case but lacks explicit when/when-not instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It states the tool checks configuration status, which implies a read-only operation, but doesn't disclose behavioral traits like what 'configured' means (e.g., valid token, permissions), error handling, or response format. The description is minimal and lacks context beyond the basic purpose.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose, making it easy to parse quickly without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what the check entails (e.g., returns boolean, error details), how it integrates with other tools, or provide context for use. For a configuration-check tool, more behavioral detail would be helpful despite the low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details (as there are none), but this is appropriate given the empty schema, warranting a baseline score above minimum.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Check') and resource ('Gemini API token configuration'), making it immediately understandable. It doesn't distinguish from siblings like 'configure_gemini_token' (which would be the complementary write operation), but it's unambiguous about what it does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. While it's implied this should be used to verify token configuration status, there's no explicit mention of prerequisites (e.g., use before calling other tools), exclusions, or how it relates to sibling tools like 'configure_gemini_token'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool edits existing files and uses reference images, but lacks details on permissions, side effects, error handling, or output format. For a mutation tool with zero annotation coverage, this is a moderate gap, though the core action is clear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences that are front-loaded with the main purpose and usage guideline. Every word earns its place, with no redundancy or fluff, making it highly efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (editing images with mutations), lack of annotations, and no output schema, the description is adequate but incomplete. It covers the basic purpose and usage but misses behavioral details like what the tool returns or potential side effects, leaving gaps for an AI agent to operate safely.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema, only implying that 'imagePath' must be exact and 'referenceImages' are optional for tasks like style transfer. Baseline 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Edit') and resource ('a SPECIFIC existing image file'), distinguishing it from sibling tools like 'generate_image' (creates new) and 'continue_editing' (continues previous edits). The specificity about modifying existing files is explicit and well-articulated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use this tool ('when you have the exact file path of an image to modify'), which implicitly distinguishes it from 'generate_image' (for new images) and 'continue_editing' (for ongoing edits). However, it doesn't explicitly mention when NOT to use it or name alternatives, keeping it at a 4.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It states this creates a 'NEW image' which implies a write/mutation operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, output format, or error conditions. The description adds basic context about creating from scratch but lacks richer behavioral details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with zero waste. The first sentence states the core purpose, the second provides crucial usage guidance. Every word earns its place, and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with 100% schema coverage but no annotations and no output schema, the description provides adequate purpose and usage guidance. However, it lacks information about what the tool returns (no output schema) and doesn't address potential behavioral aspects like generation time, quality constraints, or failure modes that would be helpful for a generative tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents the single 'prompt' parameter. The description adds minimal value by reinforcing that the prompt should describe a 'NEW image to create from scratch', but this is essentially repeating what's in the schema description. Baseline 3 is appropriate when schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Generate' and resource 'image', specifying it's 'from text prompt' and 'NEW'. It explicitly distinguishes from sibling tools by stating 'not when modifying an existing one', which contrasts with 'edit_image' in the sibling list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit usage guidance: 'Use this ONLY when creating a completely new image, not when modifying an existing one.' This clearly defines when to use this tool versus the 'edit_image' sibling alternative, with a strong exclusion statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it operates on the last image in the session (stateful behavior), supports iterative editing, and can use reference images. However, it doesn't mention potential limitations like session persistence, error handling, or output format, leaving some gaps for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose in the first sentence, followed by usage guidance and behavioral details in subsequent sentences. Every sentence adds value: the first defines the tool, the second specifies use cases, and the third explains the automatic image selection. There is no wasted text or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations and no output schema, the description does well by explaining the tool's purpose, usage, and key behavior (automatic use of last image). However, as a mutation tool with 2 parameters, it could benefit from more detail on output (e.g., what is returned) or error conditions, though the schema covers parameters adequately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents both parameters (prompt and referenceImages). The description adds no additional parameter semantics beyond what's in the schema, such as examples or constraints not captured in the schema descriptions. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('continue editing'), the resource ('the LAST image that was generated or edited in this session'), and distinguishes it from siblings by specifying it automatically uses the previous image without a file path, unlike edit_image which likely requires explicit image input. The verb+resource combination is precise and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool ('for iterative improvements, modifications, or changes to the most recent image') and provides a clear alternative context by mentioning it automatically uses the previous image, implying edit_image should be used for other images. It also distinguishes from generate_image by focusing on editing rather than creation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses key behavioral traits: it retrieves information about the 'last generated/edited image in this session,' implying session-scoped data and that it's read-only (consistent with 'get' verb). However, it doesn't specify what happens if no image exists or error conditions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is perfectly concise with two sentences that each earn their place: first states the core purpose, second provides crucial usage guidance. No wasted words, front-loaded with essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no annotations and no output schema, the description provides good context about what information is retrieved and when to use it. However, it doesn't describe the return format or what specific fields (beyond 'file path, size, etc.') are included, which would be helpful given no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters, maintaining focus on tool purpose. A baseline of 4 is appropriate for zero-parameter tools where no parameter documentation is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific verb ('Get information') and resource ('last generated/edited image'), specifying what information is retrieved (file path, size, etc.). It explicitly distinguishes this tool from its sibling 'continue_editing' by indicating this tool provides information needed for that operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance on when to use this tool: 'to check what image is currently available for continue_editing.' It clearly connects usage to a specific sibling tool and context (checking availability before continuing editing).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![Nano-Banana-MCP MCP server](https://glama.ai/mcp/servers/bongartzdiaz/Nano-Banana-MCP/badges/card.svg)](https://glama.ai/mcp/servers/bongartzdiaz/Nano-Banana-MCP)

Score Badge

Copy to your README.md:

[![Nano-Banana-MCP MCP server](https://glama.ai/mcp/servers/bongartzdiaz/Nano-Banana-MCP/badges/score.svg)](https://glama.ai/mcp/servers/bongartzdiaz/Nano-Banana-MCP)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bongartzdiaz/Nano-Banana-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server