Image Generator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPLICATE_API_TOKEN | Yes | Your Replicate API token required to use the image generation service |
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 |
|---|---|
| generate-imageC | Generate an image using Replicate's Stable Diffusion model |
| save-imageC | Save a generated image |
| list-saved-imagesA | List all saved images |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate-image | Generate an image using Replicate's Stable Diffusion model |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: generating images, listing saved images, and saving images. No overlap or ambiguity.
All tools follow a consistent verb_noun snake_case pattern (generate-image, list-saved-images, save-image), making them predictable.
3 tools is appropriate for a focused image generator server, covering the core workflow. Slightly minimal but not overly sparse.
Covers generation, listing, and saving. Missing a delete or update tool, but the core lifecycle is intact and agents can work without major gaps.