genrelay-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GENRELAY_API_KEY | Yes | Your GenRelay API key (get one at genrelay.ai). | |
| GENRELAY_BASE_URL | No | Optional base URL, defaults to https://genrelay.ai/v1 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_videoA | Generate a video with Veo 3.1, Grok Imagine or Omni Flash. Generation usually takes 1-5 minutes, longer than a tool call can wait — if it is still running when the wait budget runs out, this returns a task id to check later with check_job. Supports text-to-video and image-to-video (pass reference_images). |
| generate_imageA | Generate an image with Nano Banana Pro/2 or GPT Image 2. Usually finishes within the tool-call budget and returns the picture inline. Supports image editing and reference-guided generation via reference_images. |
| check_jobA | Check a job started earlier by generate_video or generate_image, using its task id. Returns the current status and, once finished, the download URL. |
| list_modelsA | List the video and image models this server can generate with, and what each is for. |
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 targets a distinct responsibility: generating video, generating images, checking async job status, and listing models. There is no meaningful overlap between any pair of tools.
All tools follow the same snake_case verb_noun pattern: generate_video, generate_image, check_job, list_models. The naming is uniform and predictable.
Four tools is well-scoped for a media generation relay: two generation entry points, one async status check, and one model discovery tool. Each tool earns its place without bloat or thinness.
The core workflow is covered: list available models, start generation, and poll async results. A cancellation or retry tool would make the lifecycle more complete, but it is not an obvious blocker for the stated purpose.