relay-image-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMAGE_RELAY_TOKEN | Yes | API token for authenticating with the relay service | |
| IMAGE_RELAY_BASE_URL | Yes | Base URL of the relay service, e.g. https://relay.example/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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusA | Read local configuration readiness and capabilities; no network request. |
| inspect_imageA | Fully decode a local image and report actual size, ratio, hash and alpha without modifying it. |
| generate_imageA | Generate or edit one image through the configured relay; send explicit output parameters and verify original returned bytes. No retries, resizing, model substitution or fallback. |
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 maps to a distinct operation: generating/editing an image, inspecting an existing local image, and checking server status. There is no functional overlap or plausible confusion between them.
generate_image and inspect_image follow a clear verb_noun pattern, but status breaks that pattern by being a bare noun. The naming is otherwise consistent and predictable.
Three tools is well-scoped for a small image relay server. Each tool covers a necessary, distinct responsibility without unnecessary bloat or missing basics.
The surface covers image generation/editing, local image inspection, and configuration readiness, which is complete for the stated relay purpose. No obvious dead ends or missing lifecycle operations for this narrow domain.