MCP Image Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FAL_KEY | No | API key for fal.ai | |
| IMAGE_OUTPUT_DIR | No | Directory to save generated images (default: ~/generated-images/) | ~/generated-images/ |
| TOGETHER_API_KEY | No | API key for Together AI | |
| OPENROUTER_API_KEY | No | API key for OpenRouter (default provider) | |
| REPLICATE_API_TOKEN | No | API token for Replicate |
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 |
|---|---|
| list_providersB | List all configured image generation providers and their available models |
| generate_imageC | Generate an image from a text prompt. Uses OpenRouter by default. Supports multiple providers: openrouter, together, replicate, fal. |
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 2 tools
The two tools are clearly distinct: list_providers is a read-only discovery call, while generate_image performs the actual generation action. An agent can trivially tell which one to invoke for a given need.
Both tools follow a consistent verb_noun snake_case pattern (list_providers, generate_image), matching the conventions used in the descriptions' provider references. No stylistic deviations.
Two tools is on the thin side for the stated scope: listing providers and generating images leaves no room for variations, edits, or batch operations. It is defensible for a narrow text-to-image wrapper but borderline per the rubric.
The core lifecycle of discovering providers and generating an image is covered, with sensible multi-provider support. Gaps like image editing/variations, batch generation, or generation status are absent but not fatal to the primary use case.