Skip to main content
Glama
sungmin-koo-ai

Gemini Image Generator MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GEMINI_API_KEYYesYour Google Gemini API key
OUTPUT_IMAGE_PATHYesPath to the folder where generated images will be saved

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
generate_image_from_textA

Generate an image based on the given text prompt using Google's Gemini model.

Args:
    prompt: User's text prompt describing the desired image to generate
    
Returns:
    Path to the generated image file using Gemini's image generation capabilities
transform_image_from_encodedA

Transform an existing image based on the given text prompt using Google's Gemini model.

Args:
    encoded_image: Base64 encoded image data with header. Must be in format:
                "data:image/[format];base64,[data]"
                Where [format] can be: png, jpeg, jpg, gif, webp, etc.
    prompt: Text prompt describing the desired transformation or modifications
    
Returns:
    Path to the transformed image file saved on the server
transform_image_from_fileA

Transform an existing image file based on the given text prompt using Google's Gemini model.

Args:
    image_file_path: Path to the image file to be transformed
    prompt: Text prompt describing the desired transformation or modifications
    
Returns:
    Path to the transformed image file saved on the server

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation4/5

The three tools have distinct purposes: one generates images from text, while the other two transform existing images but differ in input method (encoded data vs. file path). There is minor overlap between the two transform tools, as they serve similar functions with different input formats, which could cause slight confusion, but their descriptions clearly differentiate them.

Naming Consistency5/5

All tool names follow a consistent verb_noun_from_noun pattern (e.g., generate_image_from_text, transform_image_from_encoded, transform_image_from_file). This uniformity makes the set predictable and easy to understand, with no deviations in style or convention.

Tool Count3/5

With only 3 tools, the server feels slightly thin for an image generation domain, as it lacks operations like listing, deleting, or managing generated images. However, the count is reasonable for basic functionality, covering core tasks without being excessive.

Completeness3/5

The tools cover generation and transformation of images, which are key operations, but there are notable gaps. For example, there is no way to retrieve, update, or delete generated images, and no tools for batch processing or status checking, which could limit agent workflows in a full image management context.

Maintenance

ActivityInactive
ResponsivenessNo issues