OpenRouter Image MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | No | Your OpenRouter API key for image generation |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| configure_openrouter_tokenB | Configure your OpenRouter API token for image generation |
| generate_imageA | Generate a NEW image from text prompt using OpenRouter (Gemini 2.5 Flash Image). Use this ONLY when creating a completely new image, not when modifying an existing one. |
| edit_imageB | Edit a SPECIFIC existing image file, optionally using additional reference images. Use this when you have the exact file path of an image to modify. |
| get_configuration_statusB | Check if OpenRouter API token is configured |
| continue_editingA | Continue editing the LAST image that was generated or edited in this session, optionally using additional reference images. Use this for iterative improvements, modifications, or changes to the most recent image. This automatically uses the previous image without needing a file path. |
| get_last_image_infoA | Get information about the last generated/edited image in this session (file path, size, etc.). Use this to check what image is currently available for continue_editing. |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity: configure token, check configuration, generate new image, edit specific image, continue editing last image, and get last image info. The descriptions explicitly differentiate between generate_image (new images), edit_image (specific files), and continue_editing (last session image), preventing misselection.
All tools follow a consistent verb_noun pattern with snake_case throughout: configure_openrouter_token, continue_editing, edit_image, generate_image, get_configuration_status, and get_last_image_info. The naming is predictable and follows the same convention across all six tools.
With 6 tools, this server is well-scoped for image generation and editing. Each tool earns its place by covering essential operations: setup (configure/check), generation, editing (both specific and iterative), and session management (get last image info). This count is appropriate for the domain without being too sparse or bloated.
The tool surface provides complete coverage for the image generation and editing domain. It includes setup (configure/check), creation (generate_image), modification (edit_image and continue_editing for different use cases), and session state management (get_last_image_info). There are no obvious gaps that would cause agent failures in this workflow.