Image Generation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODEL | No | The Replicate model to use for image generation. Defaults to "black-forest-labs/flux-schnell" | |
| REPLICATE_API_TOKEN | Yes | Your Replicate API token for authentication |
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_imageC | Generate an image using the Flux model |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose of generating images using the Flux model.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'generate_image' follows a clear verb_noun pattern, and there are no other tools to cause inconsistency.
A single tool for an image generation server is too few for the apparent scope, as it lacks basic operations like listing models, managing generations, or handling variations. This minimal set will likely cause agent failures due to incomplete functionality.
The tool surface is severely incomplete for an image generation domain. It only provides generation without any supporting operations such as model selection, parameter tuning, history retrieval, or image editing, leading to dead ends in agent workflows.