Skip to main content
Glama
ion-aluminium

Nano Banana MCP Server (CLIProxyAPI Edition)

by ion-aluminium
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Nano Banana MCP Server (CLIProxyAPI Edition)

No user-submitted related servers found.

    Related Servers

    • image-gen-mcp

      ramzpat
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables generating images from text prompts using Google Gemini's native image models, with configurable aspect ratios and resolution, returning images inline or as signed URLs for larger outputs.
      -

    • Imagen MCP Server

      vipincr
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to generate high-quality images using Google's Gemini and Imagen models with support for multiple aspect ratios, dynamic model selection, and direct file saving capabilities.
      MIT

    • Nano Banana MCP

      brandon695
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables image generation and editing using Google's Gemini models with support for model selection and custom aspect ratios. Users can generate high-quality images or modify existing ones through natural language prompts while controlling specific parameters like quality and dimensions.
      -

    • Nano Banana

      saroby
      A
      license
      B
      quality
      D
      maintenance
      Enables image generation using Google Gemini models like Gemini 2.0 Flash and Imagen 3.0 with support for custom aspect ratios and negative prompts. It also allows users to list and manage generated images stored in local directories.
      2
      10 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: generate_image for image creation/editing, maintenance for system cleanup tasks, show_output_stats for statistics viewing, and upload_file for file uploading. There is no ambiguity in their functions, and an agent can easily select the correct tool based on the task.

    Naming Consistency3/5

    The naming is mixed, with generate_image and upload_file using a verb_noun pattern, while maintenance and show_output_stats are more noun-based or descriptive. This inconsistency makes the pattern less predictable, though the names are still readable and clear in intent.

    Tool Count4/5

    With 4 tools, the count is reasonable for a server focused on image generation and file management. It covers core operations without being overly sparse or bloated, though it might benefit from a few more specialized tools for advanced image editing or configuration.

    Completeness4/5

    The tool set covers key workflows: image generation/editing, system maintenance, statistics viewing, and file uploading. Minor gaps exist, such as tools for deleting uploaded files or managing image metadata more directly, but agents can likely work around these with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources