Openrouter-Nano-banana-assets-generator-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key |
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_assetA | Generate a single web asset using Nano Banana Pro. Supports reference images, color palettes, logos, and various aspect ratios/resolutions (including 2K/4K). Can generate icons, banners, backgrounds, UI elements, and more. |
| generate_asset_packB | Generate a complete pack of related web assets maintaining brand consistency. Perfect for creating cohesive sets of icons, banners, social media graphics, or UI kits. |
| edit_assetB | Edit an existing asset with fine-grained controls. Supports localized edits, lighting adjustments, focus changes, camera transformations, and more using Nano Banana Pro's advanced editing capabilities. |
| ensure_brand_consistencyC | Analyze and refine assets to ensure they follow brand guidelines. Uses Nano Banana Pro's identity preservation to maintain consistency across multiple images. |
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 4 tools
generate_asset and generate_asset_pack are clearly differentiated by single versus pack output, while edit_asset targets existing assets. ensure_brand_consistency overlaps thematically with generation features that mention brand consistency, but its analyze-and-refine role is distinct enough to avoid serious confusion.
All tool names follow a consistent verb_noun snake_case pattern: generate_asset, generate_asset_pack, edit_asset, ensure_brand_consistency. There is no mixing of camelCase, vague verbs, or inconsistent styles.
Four tools is well-scoped for an asset generation server: one for single assets, one for packs, one for editing, and one for brand consistency. Each tool covers a distinct, necessary workflow without redundancy or bloat.
The core asset lifecycle is covered: create single, create pack, edit, and enforce brand consistency. There is no explicit read/inspect or delete operation, but those are less central to a generation-focused server and agents can work around them using existing editing capabilities.