visualgen-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTPUT_DIR | No | Directory where generated PNGs and MP4s are saved. The server creates it if it doesn't exist. Defaults to './generated'. | ./generated |
| GEMINI_API_KEY | Yes | Your Gemini API key, required for accessing Google's Gemini API (e.g., for Imagen or Veo). Get it at https://aistudio.google.com/apikey. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_videoA | Submit a Veo 3.1 video generation job. Returns immediately with a job_id. Videos typically take 30-120 seconds. Call check_video(job_id) to poll for completion. The final MP4 is written to the configured OUTPUT_DIR and its absolute path is returned by check_video once ready. Args: prompt: Text description of the video to generate. model: "lite" (cheapest), "fast" (default, good balance), or "standard" (highest quality, most expensive). See get_pricing for rates. aspect_ratio: "16:9" (landscape) or "9:16" (portrait). resolution: "720p", "1080p", or "4k". "4k" is rejected for model="lite". negative_prompt: Optional text describing what to avoid. image_path: Optional absolute path to a PNG/JPEG/WebP file to use as the starting frame for image-to-video generation. |
| check_videoA | Check a video generation job. Downloads the file when ready. Returns one of three shapes:
Safe to call repeatedly. Once a job is complete or failed, subsequent calls return the cached terminal state without re-polling. Args: job_id: The id returned by submit_video. |
| list_videosA | List every MP4 file in the configured OUTPUT_DIR, newest first. Each entry has absolute path, size in bytes, and creation timestamp. |
| generate_imageA | Generate an image synchronously. Blocks until the file is on disk. Typical latency is under 10 seconds. The PNG is written to the configured OUTPUT_DIR and the absolute path is returned. Args: prompt: Text description of the image to generate. model: "nano-banana" (Gemini 2.5 Flash Image, the default — cheapest and fastest) or "imagen" (Imagen 4, higher quality, higher cost). aspect_ratio: "1:1", "16:9", "9:16", "4:3", or "3:4". negative_prompt: Optional text describing what to avoid. Ignored by Nano Banana; used by Imagen 4 when supplied. |
| list_imagesA | List every PNG file in the configured OUTPUT_DIR, newest first. Each entry has absolute path, size in bytes, and creation timestamp. |
| get_pricingA | Return current published Gemini API pricing for the models this server uses. Rates are per-image for images and per-second for video. Pricing is
hardcoded from the official docs (see the |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity. check_video monitors video jobs, generate_image creates images, get_pricing provides cost information, list_images and list_videos enumerate outputs, and submit_video initiates video generation. The separation between image and video operations is particularly clear.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming is predictable and readable: check_video, generate_image, get_pricing, list_images, list_videos, and submit_video. This consistency makes the tool set easy to understand at a glance.
Six tools is well-scoped for a visual generation server. This provides complete coverage for both image and video workflows without being overwhelming. Each tool earns its place by addressing a specific need in the generation, monitoring, listing, or pricing aspects of the service.
The tool set covers the core visual generation domain comprehensively with create, check, and list operations for both images and videos, plus pricing information. The only minor gap is the lack of a tool to delete or manage generated files, but agents can work around this using system file operations.