Gemini 2.5 Flash Image MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NAME | No | Name for the MCP server (optional) | gemini-2-5-flash-mcp |
| MCP_HTTP_PATH | No | Path for HTTP transport mode | /mcp |
| MCP_HTTP_PORT | No | Port for HTTP transport mode | 7801 |
| MCP_TRANSPORT | No | Transport mode for MCP (http for HTTP mode, otherwise STDIO) | |
| GEMINI_API_KEY | Yes | Google Gemini API key (required) | |
| MCP_HTTP_ENABLE_JSON | No | Enable JSON responses instead of SSE streaming for HTTP mode | false |
| GEMINI_IMAGE_ENDPOINT | No | Gemini image generation endpoint URL (optional) | https://generativelanguage.googleapis.com/v1beta/models/gemini-2.5-flash-image-preview:generateContent |
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
| Name | Description |
|---|---|
| generate_imageC | Generate an image from a text prompt using Gemini 2.5 Flash Image |
| edit_imageC | Edit an image using a prompt. Provide one input image via base64 or file path. |
| compose_imagesC | Compose a new image using multiple input images and a guiding prompt. |
| style_transferB | Transfer style from a style image to a base image, guided by an optional prompt. |
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
Each tool has a clearly distinct purpose: compose_images combines multiple images with a prompt, edit_image modifies a single image, generate_image creates from text only, and style_transfer applies artistic style. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern with snake_case naming: compose_images, edit_image, generate_image, style_transfer. The naming is predictable and readable throughout the set.
With 4 tools, this is well-scoped for an image generation/editing server. Each tool earns its place by covering distinct operations (composition, editing, generation, style transfer) without redundancy or bloat.
The toolset covers core image manipulation workflows: generation, editing, composition, and style transfer. A minor gap exists in lacking direct image analysis or metadata tools, but the provided tools allow agents to handle most image-related tasks effectively.