my-image-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MY_IMAGE_MCP_TOKEN | No | Token for authenticating MCP requests when listening on non-loopback addresses. | |
| MY_IMAGE_ALLOWED_HOSTS | No | Comma-separated list of allowed hosts when listening on non-loopback addresses. | |
| MY_IMAGE_PUBLIC_BASE_URL | No | Public base URL for image download links when listening on non-loopback addresses. | |
| MY_IMAGE_ALLOWED_INPUT_DIRS | No | Colon-separated (Unix) or semicolon-separated (Windows) list of directories allowed for reading local images. | |
| MY_IMAGE_ALLOW_INSECURE_HTTP | No | Set to 'true' to allow HTTP for upstream base URL (default false, only localhost allowed). | |
| MY_IMAGE_ALLOW_INSECURE_REMOTE_HTTP | No | Set to 'true' to allow HTTP for remote images (default false). | |
| MY_IMAGE_ALLOW_PRIVATE_NETWORK_URLS | No | Set to 'true' to allow private network URLs for image input (default false). |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate one or more images with the configured OpenAI-compatible Images API. Dimensions are inferred from the prompt when size is omitted. |
| edit_imageA | Edit, combine, or mask one to sixteen input images with the configured OpenAI-compatible Images API. |
| image_config_statusA | Check whether the image API is configured. This tool never returns the API Key. |
| setup_image_apiA | Create a one-time localhost setup page for Base URL and API Key. The secret is submitted locally and never passed as a tool argument. |
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 4 tools
Each tool has a clearly distinct purpose: checking config status, setting up config, generating images, and editing images. There is no overlap between the configuration tools and the image operation tools, and the descriptions make the boundaries obvious.
Most tools follow a verb_noun pattern (setup_image_api, generate_image, edit_image), but image_config_status deviates by using a noun_noun format. The inconsistency is minor and does not hinder readability.
With only 4 tools, the server is well-scoped for its purpose. Each tool is necessary and there is no bloat or redundancy, making the set easy to navigate.
The server covers the full lifecycle of image generation and editing, including configuration setup and status checks. There are no obvious gaps for its stated domain, as generation and editing are the core operations.