Gemini Image & Video Generation MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Web server port | 3070 |
| LOG_LEVEL | No | Logging level (debug, info, warn, error) | info |
| OUTPUT_DIR | No | Base directory for generated files | ./generated-images |
| CORS_ORIGINS | No | Comma-separated allowed origins | * |
| ENABLE_CACHE | No | Enable response caching | true |
| API_AUTH_TOKEN | No | Optional - API authentication token | |
| GEMINI_API_KEY | Yes | Required - Google Gemini API key | |
| MCP_AUTH_TOKEN | No | Optional - MCP server authentication | |
| RATE_LIMIT_MAX | No | Max requests per 15min per IP | 100 |
| GENERATION_RATE_LIMIT | No | Max generation requests per 15min | 20 |
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_imageB | Generate an image using Google Gemini |
| generate_videoC | Generate a video using Google Gemini Veo 2.0 |
| generate_video_from_imageC | Generate a video from an initial image using Google Gemini Veo 2.0 |
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 3 tools
Each tool targets a distinct media type and input condition: image, video, and video-from-image. No overlap or ambiguity between the three.
All tools follow a clear generate_<target> pattern, with the third adding a descriptive suffix 'from_image' that still fits the convention. Consistent and predictable.
Three tools is on the lower end but appropriate for a focused media generation server covering the core generation capabilities. Not excessively thin.
The server covers primary generation workflows (image, video, video from image). Minor gaps like image editing or video variations exist but are not essential for the stated purpose.