NanoBananaMCP
# Nano Banana by Ace Data Cloud
[简体中文安装与首用指南](https://github.com/AceDataCloud/NanoBananaMCP/blob/main/readme/README_zh_Hans.md)
<!-- mcp-name: io.github.AceDataCloud/mcp-nanobanana-pro -->
[](https://pypi.org/project/mcp-nanobanana-pro/)
[](https://pypi.org/project/mcp-nanobanana-pro/)
[](https://www.python.org/downloads/)
[](https://opensource.org/licenses/MIT)
[](https://modelcontextprotocol.io)
A [Model Context Protocol (MCP)](https://modelcontextprotocol.io) server for AI image generation and editing using [Google's Nano Banana](https://deepmind.google/technologies/imagen/) model through the [AceDataCloud API](https://platform.acedata.cloud?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_platform).
Generate and edit AI images directly from Claude, VS Code, or any MCP-compatible client.
## Use Nano Banana in Glama
Find the Ace-provided [Nano Banana source listing](https://glama.ai/mcp/servers/AceDataCloud/NanoBananaMCP) or [remote connector](https://glama.ai/mcp/connectors/io.github.AceDataCloud/mcp-nanobanana-pro). Follow the [Glama installation, API Token and first-use guide](https://github.com/AceDataCloud/NanoBananaMCP/blob/main/readme/GLAMA.md). Public discovery and a successful personal connection are separate checks; generation uses your Ace account balance.
## Nano Banana in goose
Use the independent **Nano Banana by Ace Data Cloud** native goose plugin: [install and API Token guide](goose/README.md) · [简体中文](goose/README_zh_Hans.md). It reuses this MCP server and does not imply goose Marketplace or default-provider inclusion.
## Find the Nano Banana integration in the official MCP Registry
Open [Nano Banana in the official MCP Registry](https://registry.modelcontextprotocol.io/?q=io.github.AceDataCloud%2Fmcp-nanobanana-pro), expand the matching `io.github.AceDataCloud` entry, and use its **Packages** or **Remotes** installation information in a client that consumes MCP catalogs. This is the Nano Banana integration provided by Ace Data Cloud; it is not an endorsement by the model vendor. The Registry is a directory, not the app that runs a tool.
Search for `mcp-nanobanana-pro` (or `io.github.AceDataCloud/mcp-nanobanana-pro`) to locate the exact entry. The official Registry search currently matches server names; spaces in a display title do not create extra search aliases. If your client does not consume the catalog, use the client-specific connection instructions below and check **Applications → General application** for your token, service permissions, balance and current price. Keep the original task ID when checking asynchronous results.
## Features
- **Image Generation** - Create high-quality images from text prompts
- **Image Editing** - Modify existing images or combine multiple images
- **Virtual Try-On** - Put clothing on people in photos
- **Product Placement** - Place products in realistic scenes
- **Task Tracking** - Monitor generation progress and retrieve results
## Tool Reference
| Tool | Description |
|------|-------------|
| `nanobanana_generate_image` | Generate an AI image from a text prompt using Google's Nano Banana model. |
| `nanobanana_edit_image` | Edit or combine images using AI based on a text prompt. |
| `nanobanana_get_task` | Query the status and result of an image generation or edit task. |
| `nanobanana_get_tasks_batch` | Query multiple image generation/edit tasks at once. |
## Connect: hosted OAuth, API token, or local stdio
The hosted endpoint is `https://nanobanana.mcp.acedata.cloud/mcp`. Choose one route for the MCP client:
| Route | When to use it | Credential setup |
|---|---|---|
| Hosted OAuth | The client supports remote MCP OAuth | Add only the URL, then sign in to AceDataCloud and approve access. No token needs to be pasted into client configuration. |
| Hosted API token | The client cannot finish OAuth, or you need an explicit integration credential | Send an AceDataCloud API token in the `Authorization: Bearer …` header. Keep it in a local secret store or environment variable. |
| Local stdio | The client runs a local MCP process | Install `mcp-nanobanana-pro` and pass `ACEDATACLOUD_API_TOKEN` to that process. It still calls the AceDataCloud API. |
The hosted service advertises OAuth metadata and Dynamic Client Registration (DCR). **DCR registers the client application; it is not an API key.** OAuth signs you in and the client sends the resulting Bearer token; it may reuse or create an API credential for the account. Browser sign-in still requires an AceDataCloud account. The hosted service can be metered: review [current service documentation](https://platform.acedata.cloud/documents/nano-banana-mcp?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_quick_start) and displayed pricing before a real operation. Do not configure both an OAuth login and a fixed `Authorization` header for the same server.
### Hosted OAuth examples
- **Claude and Claude Desktop chat:** Add a remote custom connector in `Customize → Connectors → Add custom connector`, enter `https://nanobanana.mcp.acedata.cloud/mcp`, select sign-in, and choose **Register automatically** if Claude asks how to register its OAuth client. Complete consent. Claude Desktop's local `claude_desktop_config.json` is a separate setup. [Claude connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).
- **Claude Code:** `claude mcp add --transport http --scope user nanobanana https://nanobanana.mcp.acedata.cloud/mcp`, then `claude mcp login nanobanana`. Check `/mcp`. [Claude Code MCP guide](https://code.claude.com/docs/en/mcp).
- **Cursor:** Add a remote server with only `https://nanobanana.mcp.acedata.cloud/mcp`. For a project, merge the entry below into `<project>/.cursor/mcp.json`; for personal use, use `~/.cursor/mcp.json`. [Cursor MCP guide](https://cursor.com/docs/mcp).
- **VS Code / Copilot:** Run **MCP: Add Server**, select HTTP, enter `https://nanobanana.mcp.acedata.cloud/mcp`, then finish the browser sign-in. New portable workspace configs use `<project>/.mcp.json`; the VS Code-specific format below uses `<project>/.vscode/mcp.json` or the user profile. Check **MCP: List Servers**. [VS Code MCP setup](https://code.visualstudio.com/docs/agent-customization/mcp-servers).
- **Codex:** `codex mcp add nanobanana --url https://nanobanana.mcp.acedata.cloud/mcp`, then `codex mcp login nanobanana`. Its user settings are in `~/.codex/config.toml`. [Official Codex MCP guide](https://developers.openai.com/codex/mcp/).
Cursor project config (OAuth):
```json
{
"mcpServers": {
"nanobanana": {"url": "https://nanobanana.mcp.acedata.cloud/mcp"}
}
}
```
VS Code-specific workspace config (OAuth):
```json
{
"servers": {
"nanobanana": {"type": "http", "url": "https://nanobanana.mcp.acedata.cloud/mcp"}
}
}
```
### Hosted API token
<!-- BEGIN TOKEN ONBOARDING -->
1. Open [Ace Data Cloud → Applications](https://platform.acedata.cloud/console/applications?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_api_key). Sign in, or register an account first.
2. Find **General application**. If it has not been created, choose **Initialize General Application**. A general key can use the services available to your account; a dedicated application's key is limited to its service. Check the required service/model access and [current pricing](https://platform.acedata.cloud/models?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_models).
3. Copy the **API Key** from the application card, or open **Keys / Manage Keys → Create** to create a separate key for this integration. Give it a recognizable name so you can revoke or rotate it independently.
4. When creating a key, review **Expiration Time**, **Set Usage Limitation**, and **Allowed APIs**. Enable only the restrictions you need, allow the operations you will call, then click **Create** and copy the token from the key list. Task lookup does not grant permission to submit a generation. Confirm the application's balance can cover your first request; any trial allowance is whatever your account currently displays.
5. Copy only the token value, without quotation marks, spaces, or `Bearer `. An API Key / API Token field expects this raw value; only a manually configured HTTP `Authorization` header needs the `Bearer ` prefix. A `platform-...` account-management token cannot replace a generation API key.


Save the key in the client's credential store or the environment variable shown below. Never put it in a prompt, shared workflow, screenshot, or Git commit. If authentication fails, check the full copied value, application/service access, expiration, usage limit, and balance before creating another key.
<!-- END TOKEN ONBOARDING -->
A fixed Bearer header bypasses OAuth. If the header is invalid, remove it before trying browser sign-in; keep the saved credential private.
For Claude Code, the shell expands the token when you add the server; treat the saved user MCP config as a secret:
```bash
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
claude mcp add --transport http --scope user nanobanana https://nanobanana.mcp.acedata.cloud/mcp \
--header "Authorization: Bearer $ACEDATACLOUD_API_TOKEN"
```
For a Claude Code project config, put a variable reference in `<project>/.mcp.json` and set that variable in the environment that launches Claude Code:
```json
{
"mcpServers": {
"nanobanana": {
"type": "http",
"url": "https://nanobanana.mcp.acedata.cloud/mcp",
"headers": {"Authorization": "Bearer ${ACEDATACLOUD_API_TOKEN}"}
}
}
}
```
Cursor uses a different environment-variable syntax in `~/.cursor/mcp.json` or an uncommitted project config:
```json
{
"mcpServers": {
"nanobanana": {
"url": "https://nanobanana.mcp.acedata.cloud/mcp",
"headers": {"Authorization": "Bearer ${env:ACEDATACLOUD_API_TOKEN}"}
}
}
}
```
In VS Code, run **MCP: Open User Configuration** and merge this server plus its masked input; `${input:...}` is for VS Code's user/workspace format and is not portable to the Agent Host `.mcp.json` format:
```json
{
"inputs": [
{"id": "acedata-nanobanana-token", "type": "promptString", "description": "AceDataCloud API token", "password": true}
],
"servers": {
"nanobanana": {
"type": "http",
"url": "https://nanobanana.mcp.acedata.cloud/mcp",
"headers": {"Authorization": "Bearer ${input:acedata-nanobanana-token}"}
}
}
}
```
For **Cline**, use its MCP configuration UI or CLI file `~/.cline/data/settings/cline_mcp_settings.json`; its remote transport value is `streamableHttp`. For **JetBrains AI Assistant**, add a remote URL from **Settings → Tools → AI Assistant → Model Context Protocol (MCP)**. For **Zed**, use a `context_servers` entry with the URL only for OAuth or add a local Bearer header. These clients have different configuration schemas; follow their current UI rather than copying another client's JSON. [Cline](https://docs.cline.bot/mcp/mcp-overview) · [JetBrains](https://www.jetbrains.com/help/ai-assistant/mcp.html) · [Zed](https://zed.dev/docs/ai/mcp).
### Local stdio
Install the package and give the local process an API token:
```bash
python -m pip install mcp-nanobanana-pro
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
mcp-nanobanana-pro
```
For Claude Desktop local MCP, merge this entry into the file opened by its developer settings (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS). `uvx` requires [uv](https://docs.astral.sh/uv/) on `PATH`:
```json
{
"mcpServers": {
"nanobanana": {
"command": "uvx",
"args": ["mcp-nanobanana-pro"],
"env": {"ACEDATACLOUD_API_TOKEN": "YOUR_API_TOKEN"}
}
}
}
```
Keep this user-level file private. Self-hosted HTTP uses `mcp-nanobanana-pro --transport http --port 8000`; expose it only with suitable network and TLS controls. Local execution still calls the AceDataCloud API.
### Check before using the service
1. `https://nanobanana.mcp.acedata.cloud/health` returning `{"status":"ok"}` checks endpoint reachability only.
2. Confirm that the MCP client loads tools. The tool list shows MCP discovery, not downstream API access or balance.
3. If you need a full API check, call `nanobanana_generate_image` with your own valid input after reviewing [current service documentation](https://platform.acedata.cloud/documents/nano-banana-mcp?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_quick_start) and displayed pricing. If the result contains a task ID, call `nanobanana_get_task` on that same ID until terminal success or failure. Do not resubmit the operation just to check progress.
For **401**, check which auth route the client used and whether the token or OAuth session is valid. A **403** may mean an account permission or content moderation failure; read the returned error. Insufficient balance and downstream service failures need their own diagnosis. A listed tool or submitted task does not prove a successful result.
## Available Tools
### Image Generation
| Tool | Description |
| --------------------------- | ------------------------------------ |
| `nanobanana_generate_image` | Generate an image from a text prompt |
| `nanobanana_edit_image` | Edit or combine images with AI |
### Tasks
| Tool | Description |
| ---------------------------- | ---------------------------- |
| `nanobanana_get_task` | Query a single task status |
| `nanobanana_get_tasks_batch` | Query multiple tasks at once |
## Supported Models
| Model | Resolution |
|---|---|
| `nano-banana` (default) | 1K |
| `nano-banana-2-lite` | 1K |
| `nano-banana-2` | 1K, 2K, 4K |
| `nano-banana-2.1` | 1K, 2K, 4K |
| `nano-banana-pro` | 1K, 2K, 4K |
All five models support generation and editing. The existing `nano-banana`, `nano-banana-2-lite`, `nano-banana-2`, and `nano-banana-pro` models also have `:official` variants. **Nano Banana 2.1 has no `:official` variant**; use exactly `nano-banana-2.1`. Omitting `model` still selects `nano-banana`.
## Usage Examples
### Nano Banana 2.1 Generation and Editing
Pass these arguments to `nanobanana_generate_image`:
```json
{
"prompt": "A blue ceramic vase on a cream background, soft side lighting, no text",
"model": "nano-banana-2.1",
"aspect_ratio": "1:1",
"resolution": "2K",
"count": 2
}
```
For `nanobanana_edit_image`, supply your reference image URL:
```json
{
"prompt": "Change the vase to green while preserving the background and lighting",
"image_urls": ["https://example.com/vase.png"],
"model": "nano-banana-2.1",
"resolution": "4K"
}
```
Generation and editing submit asynchronously. Keep the returned `task_id` and query `nanobanana_get_task` until terminal success or failure; submission alone is not a completed image. Editing without `aspect_ratio` preserves the first reference image's aspect ratio; `resolution` defaults to `1K` if omitted. Review the final image and pixel dimensions before using it.
### Generate Image from Prompt
```
User: Create an image of a sunset over mountains
Claude: I'll generate that image for you.
[Calls nanobanana_generate_image with detailed prompt]
```
### Virtual Try-On
```
User: Put this shirt on this model
[Provides two image URLs]
Claude: I'll combine these images.
[Calls nanobanana_edit_image with both image URLs]
```
### Product Photography
```
User: Place this product in a modern kitchen scene
[Provides product image URL]
Claude: I'll create a product scene for you.
[Calls nanobanana_edit_image with scene description]
```
## Prompt Writing Tips
For best results, include these elements in your prompts:
- **Main Subject**: What is the primary focus?
- **Atmosphere**: What mood should the image convey?
- **Lighting**: How is the scene illuminated?
- **Camera/Lens**: What photographic style? (85mm portrait, wide-angle, etc.)
- **Quality Keywords**: Technical descriptors (bokeh, film grain, HDR, etc.)
### Example Prompt
```
A photorealistic close-up portrait of an elderly Japanese ceramicist
with deep wrinkles and a warm smile. Soft golden hour light streaming
through a window. Captured with an 85mm portrait lens, soft bokeh
background. Serene and masterful mood.
```
## Configuration
### Environment Variables
| Variable | Description | Default |
| ---------------------------- | --------------------------- | --------------------------- |
| `ACEDATACLOUD_API_TOKEN` | API token from AceDataCloud | **Required** |
| `ACEDATACLOUD_API_BASE_URL` | API base URL | `https://api.acedata.cloud` |
| `ACEDATACLOUD_OAUTH_CLIENT_ID` | OAuth client ID (hosted mode) | — |
| `ACEDATACLOUD_PLATFORM_BASE_URL` | Platform base URL | `https://platform.acedata.cloud` |
| `NANOBANANA_REQUEST_TIMEOUT` | Request timeout in seconds | `1800` |
| `LOG_LEVEL` | Logging level | `INFO` |
### Command Line Options
```bash
mcp-nanobanana-pro --help
Options:
--version Show version
--transport Transport mode: stdio (default) or http
--port Port for HTTP transport (default: 8000)
```
## Development
### Setup Development Environment
```bash
# Clone repository
git clone https://github.com/AceDataCloud/NanoBananaMCP.git
cd NanoBananaMCP
# Create virtual environment
python -m venv .venv
source .venv/bin/activate # or `.venv\Scripts\activate` on Windows
# Install with dev dependencies
pip install -e ".[dev,test]"
```
### Run Tests
```bash
# Run unit tests
pytest
# Run with coverage
pytest --cov=core --cov=tools
# Run integration tests (requires API token)
pytest tests/test_integration.py -m integration
```
### Code Quality
```bash
# Format code
ruff format .
# Lint code
ruff check .
# Type check
mypy core tools
```
### Build & Publish
```bash
# Install build dependencies
pip install -e ".[release]"
# Build package
python -m build
# Upload to PyPI
twine upload dist/*
```
## Project Structure
```
NanoBanana/
├── core/ # Core modules
│ ├── __init__.py
│ ├── client.py # HTTP client for NanoBanana API
│ ├── config.py # Configuration management
│ ├── exceptions.py # Custom exceptions
│ ├── server.py # MCP server initialization
│ ├── types.py # Type definitions
│ └── utils.py # Utility functions
├── tools/ # MCP tool definitions
│ ├── __init__.py
│ ├── image_tools.py # Image generation/editing tools
│ └── task_tools.py # Task query tools
├── prompts/ # MCP prompt templates
│ └── __init__.py
├── tests/ # Test suite
├── deploy/ # Deployment configs
│ └── production/
│ ├── deployment.yaml
│ ├── ingress.yaml
│ └── service.yaml
├── .env.example # Environment template
├── .gitignore
├── Dockerfile # Docker image for HTTP mode
├── docker-compose.yaml # Docker Compose config
├── LICENSE
├── main.py # Entry point
├── pyproject.toml # Project configuration
└── README.md
```
## API Reference
This server wraps the [AceDataCloud NanoBanana API](https://platform.acedata.cloud/documents/nano-banana-images?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_documents_nano-banana-images):
- [NanoBanana Images API](https://platform.acedata.cloud/documents/nano-banana-images?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_documents_nano-banana-images) - Image generation and editing
- [NanoBanana Tasks API](https://platform.acedata.cloud/documents/nano-banana-tasks?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_documents_nano-banana-tasks) - Task queries
## Use Cases
- **Portrait Enhancement** - Try different clothing on the same person
- **Product Scene Composition** - Place white-background products in realistic environments
- **Attribute Replacement** - Change materials, colors, or variants
- **Poster Quick Editing** - Rapidly change styles or themes
- **2D to 3D Conversion** - Convert images to 3D product mockups
- **Image Restoration** - Restore old or damaged photos
## Contributing
Contributions are welcome! Please:
1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing`)
3. Commit your changes (`git commit -m 'Add amazing feature'`)
4. Push to the branch (`git push origin feature/amazing`)
5. Open a Pull Request
## Documentation
<!-- canonical-documentation -->
[Documentation](https://platform.acedata.cloud/documents/nano-banana-mcp?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_quick_start)
## License
MIT License - see [LICENSE](LICENSE) for details.
## Links
- [AceDataCloud Platform](https://platform.acedata.cloud?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_platform)
- [Model Context Protocol](https://modelcontextprotocol.io)
- [MCP Python SDK](https://github.com/modelcontextprotocol/python-sdk)
---
Made with love by [AceDataCloud](https://platform.acedata.cloud?utm_source=github&utm_medium=referral&utm_campaign=evergreen&utm_content=nanobanana_mcp_readme_platform)
## Cline setup / Cline 图文接入
[Nano Banana by Ace Data Cloud — English guide](https://github.com/AceDataCloud/MCPs/blob/4a2fb4e17d322bc22c5742ab3a5bd48b24ec5bdc/nanobanana/docs/cline.md) · [完整中文图文步骤](https://github.com/AceDataCloud/MCPs/blob/4a2fb4e17d322bc22c5742ab3a5bd48b24ec5bdc/nanobanana/docs/cline.md#中文步骤). The Cline marketplace submission is pending review as of 2026-10-18; the guide labels the manual fallback separately. / Cline 官方目录投稿仍待审核,手动接入不等于已上架。
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: generate_image creates new images from prompts, edit_image modifies or combines existing images, get_task retrieves single task results, and get_tasks_batch retrieves multiple task results. The descriptions reinforce these distinct roles, making tool selection unambiguous.
All tools follow a consistent snake_case pattern with the prefix 'nanobanana_' followed by a clear verb_noun combination (edit_image, generate_image, get_task, get_tasks_batch). The naming convention is perfectly uniform across all four tools, making them predictable and easy to understand.
Four tools is well-scoped for an image generation/editing server, covering core operations: generation, editing, and status retrieval (both single and batch). Each tool earns its place without redundancy, providing a complete yet manageable surface for the domain.
The tool set covers the essential lifecycle of image tasks: create (generate_image), modify (edit_image), and retrieve results (get_task and get_tasks_batch). A minor gap exists in lacking explicit deletion or management tools for tasks, but agents can work around this as the core workflows are fully supported.