opencode-image-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (logs go to stderr). | INFO |
| OUTPUT_DIR | No | Default save directory for generated images. | |
| XAI_API_KEY | No | API key for xAI provider. | |
| GEMINI_API_KEY | No | API key for Gemini provider (GOOGLE_API_KEY also accepted). | |
| GOOGLE_API_KEY | No | Alternative API key for Gemini provider. | |
| OPENAI_API_KEY | No | API key for OpenAI provider. | |
| IMAGE_MCP_MODEL | No | Default model for the custom provider. | |
| OPENAI_BASE_URL | No | Point the openai preset at a compatible proxy. | |
| IMAGE_MCP_CONFIG | No | Extra config file path. | |
| TOGETHER_API_KEY | No | API key for Together provider. | |
| DEEPINFRA_API_KEY | No | API key for DeepInfra provider. | |
| FIREWORKS_API_KEY | No | API key for Fireworks provider. | |
| IMAGE_MCP_API_KEY | No | API key for the custom provider. | |
| IMAGE_MCP_RETRIES | No | Retry attempts for 429/5xx/network errors. | 3 |
| IMAGE_MCP_TIMEOUT | No | Per-request timeout in seconds. | 300 |
| IMAGE_MCP_BASE_URL | No | Base URL for the custom provider. | |
| OPENROUTER_API_KEY | No | API key for OpenRouter provider. | |
| IMAGE_MCP_CACHE_DIR | No | Where the model cache lives. | ~/.cache/opencode-image-mcp |
| IMAGE_MCP_LOG_LEVEL | No | Alternative logging level. | INFO |
| IMAGE_MCP_MODEL_TTL | No | Model-list cache TTL in seconds. | 86400 |
| SILICONFLOW_API_KEY | No | API key for SiliconFlow provider. | |
| IMAGE_MCP_OUTPUT_DIR | No | Default save directory for generated images (alternative to OUTPUT_DIR). |
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 |
|---|---|
| list_providersA | List configured image providers and whether their API key is present. A provider only appears as |
| list_modelsA | Discover image-capable models offered by configured providers. Queries each provider's model endpoint, filters to image models, and caches
the result on disk. Set |
| add_providerA | Register any OpenAI-compatible image endpoint and remember it for later. Use this when the user names an endpoint like Parametersid:
Short handle used in Returns the discovered models plus any warnings; inspect |
| remove_providerA | Remove a provider (including built-in presets) from the config file. |
| set_default_modelA | Persist the model used when
|
| generate_imageA | Generate an image, or edit existing images, via an OpenAI-compatible provider. Model selection
If omitted, the configured default model is used. EditingPass OutputImages are always written to disk and their paths returned. Set
|
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 serves a distinct function: discovery (list_models, list_providers), provider lifecycle management (add_provider, remove_provider), configuration (set_default_model), and the core action (generate_image). There is no overlap or ambiguity in purpose.
All tool names follow a consistent snake_case verb_noun pattern: list_models, list_providers, add_provider, remove_provider, set_default_model, generate_image. The naming style is uniform and predictable.
Six tools is well-scoped for an image generation MCP server. Each tool earns its place and covers provider management, model discovery, default selection, and generation without redundancy.
The tool surface covers the full lifecycle: configure providers (add/remove/list), discover models (list_models), set defaults, and generate/edit images. No obvious gaps exist for the server's stated purpose.