OpenRouter Image Generation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_imageA | Generate images using Google Gemini API. Control image style, aspect ratio, and composition through descriptive text in your prompt. |
| list_modelsB | Show information about the Gemini image generation 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 2 tools
The two tools have clearly distinct purposes: one generates images and the other lists available models. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern (generate_image, list_models), making them predictable and easy to understand.
With only two tools, the server feels thin for an image generation service. While the core generation tool is present, the set may lack additional functionality like retrieving generation history or managing images, making it borderline.
The server covers the basic generate operation and model listing, but is missing potential features such as model selection parameter in generation, image deletion, or error handling details. This feels incomplete for a full image generation workflow.